Event Driven Architecture Fault Tolerance Pipeline

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

You are redesigning a data ingestion pipeline for a high-traffic e-commerce platform. Currently, the order management service sends data to a downstream inventory processing service using synchronous API calls. When the inventory service experiences an outage or a traffic spike, the order management service blocks while waiting for responses. This leads to timeouts and cascading failures across the platform.

You need to implement a fault-tolerant pattern to achieve the following:

Isolate failures so the order management service remains functional during inventory service outages.
Prevent cascading effects across the platform.
Ensure no data is lost and the inventory service can resume processing from the point of failure once it recovers.

Which architectural approach should you implement?

Implement an asynchronous event-driven architecture using Eventarc to decouple the services. Configure the order management service to publish events asynchronously, allowing the inventory service to resume processing from the point of failure.

Implement a graceful degradation pattern by configuring the order management service to bypass the inventory service during an outage and write a summary metric to Cloud Monitoring.

Implement a synchronous circuit breaker pattern using API Gateway to immediately return an error to the order management service when the inventory service is unavailable.

Implement a bulkhead pattern by deploying the inventory service across multiple Google Kubernetes Engine (GKE) clusters and routing traffic with Cloud Load Balancing.

Professional Cloud Data Engineer

Event Driven Architecture Fault Tolerance Pipeline

Related questions