🧩

Microservices

Service design, communication, resilience, sagas, events, observability.

20 questions
Service DesignCommunicationResilienceSagas & EventsData ConsistencyObservability

Sample Questions (20 live)

Service DesignEasy

Monolith vs microservices — when should you actually choose microservices?

InfosysTCSCognizantRead →
CommunicationEasy

How do microservices communicate — synchronous vs asynchronous, and when each?

AmazonInfosysDeloitteRead →
CommunicationEasy

What is service discovery, and why can't you just hardcode service URLs?

AmazonTCSWiproRead →
Data ConsistencyEasy

Why does each microservice own its database, and what problem does that create?

AmazonMicrosoftDeloitteRead →
Sagas & EventsMedium

How does the Saga pattern manage a transaction spanning multiple services?

AmazonMicrosoftbankingRead →
ResilienceMedium

What is the circuit breaker pattern, and how does it stop cascading failures?

AmazonMicrosoftDeloitteRead →
CommunicationMedium

What is a service mesh, and what does it offload from your application code?

AmazonGoogleMicrosoftRead →
Data ConsistencyMedium

What is eventual consistency, and how do you design a UX around it?

AmazonGoogleMicrosoftRead →
Sagas & EventsMedium

Why must event consumers be idempotent, and how do you implement it?

AmazonMicrosoftbankingRead →
Service DesignMedium

How do you manage configuration and secrets across many microservices?

AmazonDeloitteCognizantRead →
ObservabilityMedium

How do you trace a single request across many microservices?

AmazonMicrosoftGoogleRead →
ResilienceMedium

How do timeouts, retries, backoff and bulkheads work together for resilience?

AmazonMicrosoftGoogleRead →
Data ConsistencyMedium

What is CQRS, and when is separating reads from writes worth it?

AmazonMicrosoftDeloitteRead →
Sagas & EventsMedium

How does an event-driven architecture with Kafka decouple services?

AmazonMicrosoftGoogleRead →
Data ConsistencyHard

Why is two-phase commit (2PC) avoided in microservices, and what's used instead?

AmazonMicrosoftbankingRead →
Sagas & EventsHard

How does the transactional outbox pattern solve the dual-write problem?

AmazonMicrosoftGoogleRead →
Sagas & EventsHard

At-most-once vs at-least-once vs exactly-once — what's realistic in distributed messaging?

AmazonMicrosoftGoogleRead →
Service DesignHard

How do you decide service boundaries using Domain-Driven Design?

AmazonMicrosoftDeloitteRead →
ObservabilityHard

What are the three pillars of observability, and how do SLO/SLI/error budgets guide operations?

AmazonGoogleMicrosoftRead →
Service DesignHard

How do you safely evolve a service's API/events without breaking consumers?

AmazonMicrosoftGoogleRead →

Advertisement

Google AdSense slot