Data resiliency and availability are mission-critical for enterprises today—yet we live in a world where outages are an everyday occurrence. Whether the problem is a single server failure or losing connectivity to an entire data center, if your applications aren’t designed to be fault tolerant, recovery from an outage can be painful and slow. Watch this on-demand webinar to look at best practices for developing fault-tolerant applications with DataStax Drivers for Apache Cassandra and DataStax Enterprise (DSE).
View recording: https://youtu.be/NT2-i3u5wo0
Explore all DataStax webinars: https://www.datastax.com/resources/webinars
Processing transactions
must always read the most recent write
requires stronger consistency levels
Product Ratings or are using Spark for a batch job
may be tolerable to have “old” reads
could use looser, more eventual consistency levels
Processing transactions
must always read the most recent write
requires stronger consistency levels
Product Ratings or are using Spark for a batch job
may be tolerable to have “old” reads
could use looser, more eventual consistency levels
Processing transactions
must always read the most recent write
requires stronger consistency levels
Product Ratings or are using Spark for a batch job
may be tolerable to have “old” reads
could use looser, more eventual consistency levels
Processing transactions
must always read the most recent write
requires stronger consistency levels
Product Ratings or are using Spark for a batch job
may be tolerable to have “old” reads
could use looser, more eventual consistency levels
The client in this diagram hits the load balancer (LB) after the domain name system (DNS) resolves the name of the host.
The LB will then distribute the traffic within the region to the API gateway service instances in an availability zone. The
API gateway then routes the traffic to each microservice instance, that in turn sends the database requests to the nodes
in the local data center that the DataStax driver is connected to. For simplicity of the diagram, we show only a single
service type “Order Service,” but the same principles apply to applications that are composed of many services.