People always assume either there would be high-velocity development or high-scalability architecture. In theory, this would be correct at the end of the day. B

People always assume either there would be high-velocity development or high-scalability architecture. In theory, this would be correct at the end of the day. But in fact, we're far from that equilibrium. For example, here we have these two major players: Ruby: High-velocity development; Decisions have been made so you don't need to make them; Suffer from scalability issues both performance-wise and architecturally in the endgame. Java: Much slower development; Could be fast if correctly architected, but doomed as well if done wrong; Require a hell of infrastructures to work well. But you can also find some superstars among the minor players without many trade-offs, for example: Elixir: Development velocity and decision-wise are very close to Ruby; Performance is on-par or faster than Java without decisions; Messaging and cache already baked-in the language and tech stack though you don't need them in the beginning; Hire Ruby programmers and just start rollin'