3 ms·
> That seems not great for reliability and redundancy. A single server, esp. when virtualized, offers great reliability. Add regular backups in terms of disk s
by bayindirh 4y ago
> That seems not great for reliability and redundancy.
A single server, esp. when virtualized, offers great reliability. Add regular backups in terms of disk snapshots, and you'll have a "thing" which can restart in 10 seconds and rollback in half a minute.
Yes, you can do failover pretty simply, but a single server really goes a long way.
We redundantly install critical servers, but the backup doesn't kick-in unless the other one halts and catches fire (sometimes literally).
- hedora 4y agoIf you want to go the enterprise route, you can mount the VM on an on-prem block store with a secondary ~ 10-20ms away, and set it to async or sync replication mode. If the primary DC burns down (hey, it happens!), you just fail over and lose ten or zero seconds of transactions, respectively. Downtime is roughly time to detect the outage + time it takes to reboot the primary. You can also do this in the cloud, of course, but I've found that grounding the implementation in a physical example clarifies exactly what I'm talking about. Some people claim this isn't a "high availability" solution, since you need to take the service down while you reboot for OS patches, etc, and during those windows, all requests fail. However, that's often fine. In particular, these sorts of setups can easily hit five nines, which is as good as an AWS region. However, in normal operation, they don't spuriously generate error codes like S3, etc do. If you count your SLA as "service went 1 minute without generating a spurious error for any client", then this will have many more 9's than a microservice architecture. If you count your SLA as "at least one request returned 200 in a 1 minute window", then the two approaches will probably be comparable, at least until you start running the microservices in multiple AWS regions (or whatever) and eliminate outages due to human operator error.
- rdsubhas 4y agoWhat about simple stuff, like updating the kernel for the latest security patch and needing a small restart?
- bayindirh 4y agoNone of the pets we run complain when the service is not available for a minute or so, which is required to restart a system in the worst case scenario. Even we don't blindly restart our cattle servers. We drain & restart them, which means the load is already shifted to other servers in the fleet.
- rdsubhas 4y agoYou missed the context of the comment. Comment was for the single-server, not for 2+ let alone fleet :)
- bayindirh 4y agoI meant that, most of the time we can install a single server which is used by a whole fleet, and that single server doesn’t get restarted unless we update it, because they’re reliable.