Conceptual
Browse Instruct Curate
Login

About Microservices Architecture: Decomposition, Communication, and Failure

Copied

How to split a system into independently deployable services and keep it correct when the network fails. You will be able to decompose a domain into bounded contexts, choose between synchronous and asynchronous communication, maintain data consistency without distributed transactions using sagas and the outbox pattern, contain failures with circuit breakers and bulkheads, trace requests across services, and argue honestly for a monolith when that is the better answer.

Estimated Time to Complete

Only available after login

What You'll Learn

Concepts:
Distributed Tracing API Gateway Pattern Retry with Exponential Backoff Eventual Consistency Circuit Breaker Pattern Synchronous vs Asynchronous Service Communication Monolith-First Strategy Idempotency Bulkhead Pattern Service Discovery Database-per-Service Pattern Saga Pattern Bounded Context Transactional Outbox Pattern Service Decomposition by Business Capability Consumer-Driven Contract Testing

What you will learn

No introduction video available

About Demerzel

D

Guide profile coming soon.