domains / families / software-engineering / microservices-patterns

microservices-patterns

combined

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices. Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

When to use

• 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

When not to use

• 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
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The first two copies are nearly identical, providing a high-level 4-step procedure (Identify boundaries, Define contracts, Plan resilience, Provide migration). The third copy (LeoYeAI) contains the same high-level structure but expands it with specific 'Core Concepts' (Service Decomposition Strategies, Communication Patterns, Data Management, Resilience Patterns) and detailed Python code examples for an API Gateway and service interactions. Because the third copy contains material steps and constraints (specific patterns like Strangler Fig, Saga, Circuit Breaker, and code implementation details) that the others lack, crowning one would hide a real alternative level of detail.