2 ms·
This is pretty much my thought. I lead a jumpstarted development effort for a startup last year (we used an agency to get through the initial build). We looked
by SkyPuncher 8y ago
This is pretty much my thought. I lead a jumpstarted development effort for a startup last year (we used an agency to get through the initial build). We looked into several options, but ultimately decided to use Rails. Why? We all knew exactly what we could expect from Rails and we knew we could get it to work in the way we wanted without too much hassle.
Sure, we might hit growth problems in years but we can cross that bridge down the road.
- aantix 8y agoI consulted on a site that could get 50 million unique users in any given month, sometimes with large bursts of traffic. A heavy read site is trivial to scale these days. Serve static assets from CDNs, fragment cache the views, horizontally scale when needed. Rinse, repeat.
- sho 8y agoExactly. I've also been involved with read-heavy Rails sites serving well in excess of 1000reqs/sec, and I know that others sites (Shopify et al) do way more. As you point out, it's all about having an intelligent caching strategy and extensive use of CDNs. Most scaling issues I've seen on well-designed Rails sites have been to do with the DB, not the framework!