3 ms·
There are more issues than just raw performance, or only raw performance. Right now, I'm working for a web services company where the vast majority of our work
by tracker1 9y ago
There are more issues than just raw performance, or only raw performance. Right now, I'm working for a web services company where the vast majority of our work is via an API with a limited range of request types. We have external(locally cached) and internal data sources that all have to be queried, and dealt with before the logic can work and a response can be returned.
We're currently niggling over a few ms here, and a few there. Balancing the cost of adding more servers to distribute load. Migrating from colocation to cloud hosting in order to scale more seamlessly (iirc, over 150% growth yearly or more). Our SQL database has been a big bottleneck, moving heavy loads out of SQL and into more appropriate separate data stores.
Just because it's only an extra 100ms, doesn't mean it doesn't matter, as it's not the only link in the chain. I would never, for example use rails for an API service... it's too expensive on top of everything else.
Right now we have a fair amount of C#, a bit of Node, and may consider some go for future use in pieces. It comes down to picking the right things... It also depends on what/where you're using the technology.