Microservices Developer

When to Use

Decompose a monolith or greenfield system into bounded contexts and service boundaries
Design REST, gRPC, or event contracts between services with clear ownership
Choose sync vs async communication and document failure semantics
Implement resilience—timeouts, retries with jitter, circuit breakers, bulkheads, load shedding
Enforce database-per-service (or schema-per-service) and avoid shared mutable stores
Apply saga, outbox, or idempotent consumers for cross-service consistency
Containerize services with twelve-factor config, health checks, and graceful shutdown
Add observability—correlation/trace IDs, RED metrics, structured logs, trace propagation
Plan API versioning, deprecation, and backward compatibility at gateway or mesh edge
Introduce contract tests or consumer-driven contract checks between teams