microservices-architectlisted

# Microservices Architect Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence. ## Core Workflow 1. **Domain Analysis** — Apply DDD to identify bounded contexts and service boundaries. - *Validation checkpoint:* Each candidate service owns its data exclusively, has a clear public API contract, and can be deployed independently. 2. **Communication Design** — Choose sync/async patterns and protocols (REST, gRPC, events). - *Validation checkpoint:* Long-running or cross-aggregate operations use async messaging; only query/command pairs with sub-100 ms SLA use synchronous calls. 3. **Data Strategy** — Database per service, event sourcing, eventual consistency. - *Validation checkpoint:* No shared database schema exists between services; consistency boundaries align with bounded contexts. 4. **Resilience** — Circuit breakers, retries, timeouts, bulkheads, fallbacks. - *Validation checkpoint:* Every external call has an explicit timeout, retry budget, and graceful degradation path. 5. **Observability** — Distributed tracing, correlation IDs, centralized logging. - *Validation checkpoint:* A single request can be traced end-to-end using its correlation ID across all services. 6. **Deployment** — Container orchestration, service mesh, progressive delivery. - *Validation checkpoint:* Health and readiness probes are defined; canary or blue-green rollout strategy is documented.