Microservices Patterns

This one guides you through decomposing monoliths and designing distributed systems with proper service boundaries, communication patterns, and resilience strategies. It covers the practical stuff like defining contracts, managing distributed data, implementing service discovery, and planning migrations. Comes with an implementation playbook that walks through patterns and examples. The honest take: microservices add real operational complexity, so the skill explicitly tells you when not to use it, like when you're building a prototype or don't have the ops team to support distributed systems. Good guardrails for teams who need to make the monolith vs microservices call based on actual constraints, not hype.