Building for the (Inevitable) Next Cloud Outage


Authors:   Pavel Nikolov


The presentation discusses the use of eventual consistency in microservices deployment to address data consistency, latency, reliability, and disaster recovery problems.
  • Microservices deployment can benefit from eventual consistency
  • Eventual consistency can address data consistency, latency, reliability, and disaster recovery problems
  • Hosted database solutions may not provide 100% consistency and may be a single point of failure
  • Long-running connections need to be reconnected to ensure high availability
The presenter demonstrated how their system achieved high availability and low latency by using Nuts Jetstream and BGP to propagate events and handle disaster recovery. They also showed how eventual consistency can be used to address data consistency problems in microservices deployment. The presenter emphasized the importance of reconnecting long-running connections to ensure high availability.


It seems that every few months we hear about the widespread impact of a major cloud outage. Cloud outages are unpredictable and inevitable; this is what keeps SRE teams up at night. Public cloud remains the most popular data center approach among the cloud native community, with multi-cloud growing in adoption. However, adopting a multi-cloud strategy isn’t as simple as hitting the go button. In this session, we will demonstrate how to deploy a Kubernetes application across clusters in multiple clouds and regions with built-in failover to automatically adapt to cloud outages. You will witness how BGP directs traffic across clusters in a healthy state. Then, we will take one of the clusters offline and show how workloads are automatically rescheduled and traffic is rerouted to healthy clusters in real-time. We will dive into the technologies and logic that are driving this engine and discuss how you can build this type of resilience into your own applications.Click here to view captioning/translation in the MeetingPlay platform!