Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureMedium

A financial services company is building a new real-time fraud detection system using a microservices architecture. They need to ensure that transactions are processed quickly and reliably, and that any issues can be identified and resolved without affecting other services. The team plans to use a mechanism to isolate failures and prevent them from cascading across the system. Which pattern is most suitable for this requirement?

  1. ABulkhead Pattern
  2. BStrangler Fig Pattern
  3. CSidecar Pattern
  4. DSaga Pattern
Show answer & explanation

Correct answer: A. Bulkhead Pattern

The Bulkhead Pattern is designed to isolate services into separate resource pools (like threads, connection pools, or even physical machines) to prevent a failure in one service from cascading and overwhelming others, fitting the requirement to isolate failures.

Why the other options are wrong

  • B. The Strangler Fig Pattern incrementally migrates a monolithic application to microservices by gradually replacing functionalities.
  • C. The Sidecar Pattern deploys a helper container alongside a main application container to extend its functionality.
  • D. The Saga Pattern manages distributed transactions across multiple services to maintain data consistency.

Bulkhead Pattern

A design pattern used in microservices to isolate failures by partitioning components into separate groups. If one group fails, the others continue to function.

  • Prevents cascading failures.
  • Isolates resources (e.g., thread pools, connection pools).
  • Enhances fault tolerance and resilience.

Memory trick: Resilience patterns: Bulkhead isolates, Saga coordinates, Strangler migrates, Sidecar extends.

More Cloud Native Architecture questions