(no title)
drewbailey | 7 years ago
The vast amount of projects and internal tools out there don't need to be "webscale" or process millions of requests a minute.
drewbailey | 7 years ago
The vast amount of projects and internal tools out there don't need to be "webscale" or process millions of requests a minute.
dasil003|7 years ago
If you need raw single process performance especially with parallelism then you probably should look beyond ruby. But the whole Rails doesn’t scale because Twitter meme is asinine.
toasterlovin|7 years ago
6t6t6t6|7 years ago
Really, the vast majority of web apps built today will see hundreds of requests per minute.
Still, Github and Shopify have proven that Rails can scale to hundreds of thousands of requests per second. Which is a great number.
Said that, if my goal was to build an app with a simple set of features that don't change often, and that will serve 100 million users, where none of them is paying user, I would probably not choose Rails.
khalilravanna|7 years ago
What would you choose in this case? I'm also a little confused where the user "paying" comes in. Is that in terms of the importance of that specific type of interaction or the concern of friction scaring of "free" users?
ericb|7 years ago
Retric|7 years ago
They are dwarfed by most media companies etc. Github's website sees far less than 1% of Facebook's traffic for example. On the other hand they have almost 30 million users so they are not exactly tiny.
drewbailey|7 years ago
Rails allows companies to grow quickly and focus on attracting users and delivering business value at the sacrifice of a re-write or complexity of managing rails and performance issues down the road.
mirceal|7 years ago