Enterprise Systems Built with Microservices are Designed to Expect Failures

September 29, 2018
Designing systems for failures between any service call is enshrined as a key principle in Microservices architecture. Implementing Circuit Breaker pattern helps reduce service call failures from cascading into entire system failure. And adopting an Eventual Consistency paradigm, with streaming platforms, helps by decoupling cross microservices communications. But we still need additional strategies to not only build resilient systems, but also systems that reduce transactional, or end-user experienced failures. We'll explore the use of caching frameworks to improve resilience and performance in enterprise microservices systems. Lets look at how Redis, Pivotal Cloud Cache, and Hazelcast can help system handle failures! Speaker: Dalia Borker Vice President, JP Morgan Chase
Previous
Cloud-Native Streaming Platform: Running Apache Kafka on PKS (Pivotal Container Service)
Cloud-Native Streaming Platform: Running Apache Kafka on PKS (Pivotal Container Service)

Next Video
Mission Impossible: Deploying Pivotal Cloud Foundry to Nine Air Operational Sites in a Year
Mission Impossible: Deploying Pivotal Cloud Foundry to Nine Air Operational Sites in a Year

The Air Operations Center (AOC) commands and controls all planning and execution of air missions for the Un...

Enter curious. Exit smarter.

Learn More