microservices-patterns

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

View Source
name:microservices-patternsdescription:Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

Microservices Patterns

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

Use this skill when

  • Decomposing monoliths into microservices

  • Designing service boundaries and contracts

  • Implementing inter-service communication

  • Managing distributed data and transactions

  • Building resilient distributed systems

  • Implementing service discovery and load balancing

  • Designing event-driven architectures
  • Do not use this skill when

  • The system is small enough for a modular monolith

  • You need a quick prototype without distributed complexity

  • There is no operational support for distributed systems
  • Instructions

  • Identify domain boundaries and ownership for each service.

  • Define contracts, data ownership, and communication patterns.

  • Plan resilience, observability, and deployment strategy.

  • Provide migration steps and operational guardrails.
  • Resources

  • resources/implementation-playbook.md for detailed patterns and examples.