5 ms·
There's also old fashioned performance improvements. Most enterprise software has plenty of room for improvement there. I've noticed a correlation between peopl
by flukus 10y ago
There's also old fashioned performance improvements. Most enterprise software has plenty of room for improvement there. I've noticed a correlation between people that push for distributed systems and ones that don't know how things like indexes and transactions work or the need to avoid n+1 queries.
I'm sure some apps need to be distributed systems, but I bet it's a tiny minority.
- LoSboccacc 10y agothere's also availability, especially for enterprises. so redundant frontend and master/slave db at least. may or may be not distributed, according to one's personal definition of distributed.
- UK-AL 10y agoPeople who actually know how to build distributed systems would understand transactions and indexes.
- apeace 10y agoYes, that's exactly my point. This article makes it sound like you need a distributed system at almost any level of scale. Yet the reality is, you only need one of you are doing tons of writes. Most systems are read-heavy, which is why most people scale reads horizontally instead of using a distributed system.
- mazerackham 10y agoMore or less agree with your point, just wanted to point out that scaling reads horizontally usually means adding a distributed quality to your system, and not understanding how that impacts the system can have bad side effects
- flukus 10y agoWhere do you draw the line of where a horizontally scalable system begins? Scaling reads might only involve a caching server, but most of us probably wouldn't consider an app server with a cache to be distributed.
- MR4D 10y agoGiven that HN runs on a single server [ https://news.ycombinator.com/item?id=9222006 https://news.ycombinator.com/item?id=9222006 ], I'd be very willing to take your side of the bet.