Training Agenda

Microservices Patterns

Microservices solve real problems — independent deployability, team autonomy, technology flexibility — but they introduce distributed systems complexity that monoliths never had. The patterns that make microservices work in practice are not about splitting code into small pieces; they are about managing data consistency, service communication, failure isolation, and operational overhead. This training covers the patterns that experienced microservice practitioners rely on, with concrete implementation examples.

2 days On-site, remote, or hybrid Up to 20 participants German or English
What We Cover
The patterns that make microservices actually work
Day 1

Decomposition, Communication & Data

  • Service decomposition: decompose by business capability vs subdomain — getting boundaries right
  • The database-per-service pattern: why it matters and what it costs
  • Saga pattern: managing distributed transactions — choreography vs orchestration sagas
  • Outbox pattern: reliable event publishing without distributed transactions
  • API composition: aggregating data from multiple services for queries
  • CQRS for microservices: separate read and write models at the service level
  • Synchronous communication: REST, gRPC — service discovery, load balancing, circuit breaking
  • Asynchronous messaging: event-driven integration between services, event schema design
  • API gateway: single entry point, auth, rate limiting, routing
  • BFF (Backend for Frontend): tailored APIs per client type
Day 2

Resilience, Observability & Operations

  • Resilience patterns: circuit breaker, bulkhead, retry with exponential backoff, timeout
  • Health checks and readiness probes: Kubernetes integration
  • Distributed tracing: correlation IDs, OpenTelemetry across services
  • Log aggregation: structured logging with service and trace context
  • Service mesh vs application-level resilience: when each makes sense
  • Testing microservices: consumer-driven contract tests with Pact, integration testing strategies
  • Configuration management: externalized config, secrets management
  • Deployment patterns: blue-green, canary, feature flags at the service level
  • Anti-patterns: distributed monolith, chatty services, shared databases, nano-services
Learning Outcomes
What your team walks away with

Teams building or operating microservice architectures who need the patterns — not just the theory — to handle data consistency, resilience, and operational complexity.

Book the Microservices Patterns training

Best suited for teams already running microservices who are hitting the hard problems — or teams planning the move who want to avoid them.

Get in touch