Re:There's Just No Getting Around It: You're Building a Dist...
by MR4D on Sunday April 30, 2017 @03:53PM
(#14233491)
Given that HN runs on a single server [ https://news.ycombinator.com/item?id=9222006 ], I'd be very willing to take your side of the bet.
Re:There's Just No Getting Around It: You're Building a Dist...
by apeace on Friday April 28, 2017 @07:01AM
(#14218396)
Yes, 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.
Re:There's Just No Getting Around It: You're Building a Dist...
by mazerackham on Saturday April 29, 2017 @02:49PM
(#14228075)
More 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
Re:There's Just No Getting Around It: You're Building a Dist...
by flukus on Monday May 01, 2017 @05:56AM
(#14236495)
Where 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.
Re:There's Just No Getting Around It: You're Building a Dist...
by LoSboccacc on Friday April 28, 2017 @05:19AM
(#14217997)
there'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.
I'm sure some apps need to be distributed systems, but I bet it's a tiny minority.