|
|
|
|
|
by pbh
5379 days ago
|
|
I'm not an expert, but this is what I've cobbled together as a fellow Ruby/Rails startup person. Fault Tolerance: Just use Heroku. We've seen maybe an hour of downtime in a few months? Speed (and fault tolerance): Cache everything you can, assets on S3/CF. Testing: Rails Test Prescriptions by Noel Rappin
[http://pragprog.com/book/nrtest/rails-test-prescriptions]. Then you can choose what you like, but I like Test::Unit, Mocha, FactoryGirl. Code Abstraction: Rails is already pretty sensibly organized, and if MVC + tests + static assets is not a good fit for your webapp, you really should not be using it in the first place. One minor point: Noel and others will tell you to use skinny controllers. Curious what other people consider best practice for Ruby/Rails startups. |
|
This is terrible advice. Telling developers to cache everything is like walking into a rehab clinic with Lindsay Lohan's purse.
Cache what you can measure as having a performance problem, which can't be optimized in another way. It should always be used as a last resort.