microservices-architectlisted

# Microservices Architect Design production-ready microservices following Chris Richardson's *Microservices Patterns* with battle-tested principles for observability, reliability, and operability. ## Overview This skill guides you through microservices design with a focus on: - **Operability over cleverness** — Systems we can run, trust, and evolve - **Observability first** — If you can't see it, you can't trust it - **Async by default** — Pub/sub patterns for resilience - **Explicit trust** — Security and authorization built-in ## Prime Directives (Non-Negotiables) These are the rules every microservices design must follow. Exceptions require explicit justification. | # | Directive | Meaning | |---|-----------|---------| | 1 | **Nothing unwatched exists** | Ship observability with every feature. Know before customers. | | 2 | **Produce it → publish it. Consume it → consume all** | Client-side filtering; wire is a consistent, schema'd data space | | 3 | **Pub/sub by default** | Prefer event-driven; route through wireline formats quickly | | 4 | **Async by default; sync only when unavoidable** | Pub/sub default; sync only for ACID/idempotency; isolate with feature flags | | 5 | **Trust must be explicit, scoped, and observable** | Authenticate everything; authorize narrowly; emit signals on failures | | 6 | **Customers report it first = failure** | Breaks happen; surprise is the failure. Detect before impact. | | 7 | **Observability over performance** | Accept 20-30% over