4 ms·
This is a question that I have spent a ridiculous amount of time pondering. My conclusions so far are this: Single node application systems are by far the mos
by bob1029 5y ago
This is a question that I have spent a ridiculous amount of time pondering.
My conclusions so far are this:
Single node application systems are by far the most reliable and manageable from a business logic standpoint. At no point does spreading a problem across more than 1 computer make that problem easier to solve.
If you are concerned about latency, you need to get really abstract with your problem and ask what is even possible in information theoretic terms. If you are truly constrained to 1 serialized, synchronous context (i.e. a competitive counterstrike match or a stock exchange), there is little you can do to alleviate the root problem as your users get further from the server. You can certainly look at using some consensus protocol like multi-paxos, but then your transaction latency goes from microseconds (if you were clever) to milliseconds, representing orders of magnitude slowdown in the typical case.
The best solution I can come up with is a synchronously-replicated append-only log store which is utilized in a primary/sync-witness/async-witness/... configuration. The first tier of resilience would be synchronous and provided by a set of witness nodes which must ack as a majority to progress primary. These nodes would ideally be within 1-2ms of the primary. The async witnesses could be in orbit and/or on mars. These are more about extreme geological disaster recovery. The witness nodes would also use a separate consensus protocol to decide when the primary needs to be taken down and replaced with a sync (or god forbid async) witness. They would be able to elect an emergency leader separate from the primary who would be authorized to stop the bad primary in the hypervisor, and edit any relevant DNS records to ensure traffic stops hitting the bad system.
For the customers I work with, it is wayyy easier to build & sell a system that operates on a single box with sync replication + manual failover. Our customers are tolerant to production having a brief outage for a few minutes during the business day. Especially considering the fact that I have still never had to do this exercise in a production setting. The hardware we run this stuff on is so ridiculously stable.
- gravypod 5y ago> Single node application systems are by far the most reliable and manageable from a business logic standpoint. Manageable? Maybe. Reliable? No. Most companies don't need it but if a pipe bursts above the server room and now all of your medical records for your hospital are unavailable you're going to have a bad time. > At no point does spreading a problem across more than 1 computer make that problem easier to solve. I don't think anyone claimed it was easier (yet). The main thing people strive for is: 1. Dynamically reshaping your compute needs to match any needs. 2. Surviving failures of nodes or crashes in your application. 3. Managing all of the BS that goes with obtaining this (logs, etc). > Especially considering the fact that I have still never had to do this exercise in a production setting. The hardware we run this stuff on is so ridiculously stable. I hope this isn't the case but this sounds like quite the death flag.
- brian_cunnie 5y agoI’ve only seen one burst pipe bring down a computer (Pitney Bowes, 1995), but I’ve witnessed several S3 outages.
- zthrowaway 5y agoYou should spend a week working on a infra / ops team then.
- Demiurge 5y agoI worked with multiple ops/infra teams, and have seen standard server rooms and advanced server rooms. They’re not supposed to have pipes leaking on the racks, that’s ridiculous. I know many stable redhat servers that didn’t need to reboot for years. I also maintain websites on hetzner servers that haven’t needed to reboot in years, under pretty high load. On the other hand, I got a hostnoc dedicated server and that thing went offline three times a month. So yeah, you have to know what you’re doing regardless of whether you’re building a server room or a k8s cluster.
- mwcampbell 5y ago> I know many stable redhat servers that didn’t need to reboot for years. That's not actually something to brag about, as it implies they weren't receiving important kernel updates, particularly security updates.
- bob1029 5y agoSo, we do ~daily restarts on our customers' systems. We have a solid 12 hours per day to patch up a server before it needs to be in production again. That said. We communicate directly with other systems on the same premises that probably haven't been rebooted in over a decade. Building something that can run 10 years without downtime is not happenstance. It is very intentional and deliberate engineering.
- 5y ago