3 ms·
I don't want to put words into your mouth, but I want to clarify something. Those 90s style architectures that had database servers, application servers, cachi
by kasey_junk 13y ago
I don't want to put words into your mouth, but I want to clarify something. Those 90s style architectures that had database servers, application servers, caching servers etc (N-tier) were not about scaling the number of connections you could support on a given set of hardware or maximizing message throughput through a system or minimizing message latency. Those architectures came about as a response to a common problem of the time which was lots of different legacy systems needing to talk to each other.
Think accounting systems on a mainframe talking to inventory systems written in C talking to HR systems provided by the consultantware flavor of the month. In those kinds of environments it made a ton of sense to break up the various functional tiers so that you could attach to the appropriate one with minimal translation layers.
Having worked on systems like that in the past, you'd never go in thinking that it is the lowest latency way to do it. Latency wasn't typically a major design driver.
That said, I work on low latency message systems now and the architecture your describing is very typical in that space.
- erichocean 13y agothe architecture your describing is very typical in that space Totally, and whatever innovation I actually produce is mainly putting together cool stuff other people have done in a novel way (which at times, hardly seems innovative). I'm hugely indebted to all of the research and pioneers in production in our industry. One of the things I love about CS is how easy it is to take cool shit from one subfield and apply it to another. There's just so many smart people figuring stuff out that to a guy like me, that's like Christmas every week. :)