Live data from Hacker News

Distributed systems programming has stalled

shadaj.me

231–232 of 232 posts

Re: Distributed systems programming has stalled

#231

Earlier quoted context omitted.

I've found the rush to distributed computing when it's not strictly necessary kinda baffling. The costs in complexity are extreme. I can't imagine the median company doing this stuff is actually getting either better uptime or performance out of it—sure, it maybe recovers better if something breaks, maybe if you did everything right and regularly test that stuff (approximately nobody does though), but there's also so…

Distributed or not is a very binary function. If you can run in one large server, great, just write everything in non-distributed fashion. But once you need that second server, everything about your application needs to work in distributed fashion.

[dead]

Re: Distributed systems programming has stalled

#232
post #226

Earlier quoted context omitted.

I couldn't disagree more. My principle is to write systems extremely simply and then distribute portions of it as it becomes necessary. Almost always it never becomes necessary and the rare cases it does, it is entirely straight forward to do so unless you have an over-complicated design. I don't think I've ever seen it done well when done in the opposite direction. It's always cost more in time and effort and result…

Tons of vendors offer cloud first, distributed deployments. Erlang is distributed by default. Spark is distributed by default. Most databases are distributed by default.

[dead]
Post reply on HN