133 comments posted · 10 followers · following 11
However, all of this hinges on the fact that you REGULARLY test these systems. I have heard far too many stories of people who have disaster recovery systems in place only to not test them regularly to find their backup takes just as long to bring up than it would to completely rebuild from scratch.
It also helps to have some type of automated build system that stores all your production builds as backups. That way when you do have failure that maybe code related you roll back the database and grab the last good prod build and bring your systems back up.
here is a list of 50 ror sites -http://storecrowd.com/blog/top-50-ruby-on-rails-w...
Then you have to figure in the container that your application is going to run in. JBOSS vs tomcat, commercial support or not etc...
Ruby is a fairly cheap way to get going considering its highly active community. Then with cloud based services like Heroku it makes it really easy to scale.
Java is cheap to start with but can get expensive very fast if you dive into the EE side of things.
After that IRC > *. If you ask intelligent questions there are pleanty of people on servers like freenode who can help you find what you need or even just answer the question straight up. Channels like ##java have people who work for companies like JBOSS and deal with the internals of the language on a daily basis. Just idling in the channel is a good way to pickup information as well.
But that's amazing that it snowed last night.