Running on rails not only increases Dev expense but also the operational expense since you would need more servers to handle a similar load. (Correct me if this has changed with Ruby 3)
Running on rails not only increases Dev expense but also the operational expense since you would need more servers to handle a similar load. (Correct me if this has changed with Ruby 3)
Thinking out loud here, say you can only serve 200rqs with Rails but 2000rqs in some other framework (yes not fair comparison, endpoints matter etc etc). That means you need 10x the servers but take a step back a sec. 200rqs is 720k a hour or 17,280,00 a day or 518,400,000 requests a month. (The scale for that is pretty high already). I'm pretty sure the 10x increase you need in servers will cost less than 1 extra employee at say $70k a year.
If this were true, startups wouldn't be paying a third of the money they raised to AWS.. considerably more than people cost.
Companies grow and this 1/10th efficiency will quickly multiply.
They're paying that because they and their investors want to. If you look beyond that it's absolutely possible to get that infrastructure at a tenth of the AWS cost by going with old-school bare-metal providers such as OVH or Hetzner, but then it means you no longer get to brag about how you wrangle (self-inflicted) complexity with Terraform and tons of YAML files at the next AWS conference.