4 ms·
Web servers are usually trivially horizontally scalable. You must have had significant in-memory shared state to encounter that problem. Right? Had you adopte
by paulddraper 7y ago
Web servers are usually trivially horizontally scalable.
You must have had significant in-memory shared state to encounter that problem. Right?
Had you adopted a less stateful model, you'd have looked rather pretty with two Java servers.
- lmm 7y ago> You must have had significant in-memory shared state to encounter that problem. Right? "Significant" is in the eye of the beholder. The core of the system was easy to make shardable. But you'd be surprised how many implicit assumptions creep in, how easy it is for ancillary parts to end up sharing state when it's easy. Also note that just because your state's in a database doesn't mean having two instances of the thing that accesses it will work, you can easily end up with an access pattern that assumes only one reader (for example) even though on paper there's no in memory state. > Had you adopted a less stateful model, you'd have looked rather pretty with two Java servers. Maybe. At the point where we're running 4 or 8 servers we'd have been facing much the same ops problems that they were. Java bought us an extra year or two of not having to deal with that, but also a significant amount of migration work when it just became impossible to stick to the single process model. At the end of the day we still kept the 5x latency advantage, which is definitely not nothing. But there were also definitely features that they brought to market quicker, and I'm pretty sure Ruby played a part in that. Tradeoffs, tradeoffs everywhere. I left before the final outcome of that fight (for all I know it's still ongoing), but I don't think either company was being dumb.
- paulddraper 7y ago> At the point where we're running 4 or 8 servers we'd have been facing much the same ops problems that they were. Yes and no. You'd need some ops work, but you'd need to worry a lot less about managing your infrastructure provisioning to keep costs low, e.g. reserved instances, dynamic scaling, etc. and putting out fires when you inevitable exceed your tight perf margins. You could overprovision 24/7 by 50% and write it off. Your competitors couldn't.
- gerbilly 7y ago> Web servers are usually trivially horizontally scalable. Maybe he really meant to say 'application server'. I.e that there was server side code with non trivial compute/memory requirements for running business logic.
- paulddraper 7y agoBy "web server", I meant (Java) "application server".