skills.rest
p-o-ke-nae
p-o-ke-naeCOMMUNITY
Explore all skills by this author →
GitHub

microservices-patterns

Design resilient microservices architectures with service boundaries and communication patterns.

Updated May 16, 2026
Search Tags:#microservices#resilience#event-driven#distributed-systems#saga#circuit-breaker#service-boundaries
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill microservices-patterns-p-o-ke-nae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/microservices-patterns
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill microservices-patterns-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design microservices systems that are split cleanly, communicate reliably, and remain resilient under failure.

Core Features & Use Cases

  • Service Decomposition: Split a monolith into bounded services by business capability or domain.
  • Communication Patterns: Choose REST, gRPC, queues, or event streams for synchronous and asynchronous workflows.
  • Resilience and Transactions: Apply circuit breakers, retries, bulkheads, and sagas to reduce outages and coordinate distributed work.
  • Use Case: Use it when planning an e-commerce backend with separate order, payment, and inventory services.

Quick Start

Ask me to design a microservices architecture for your application and include service boundaries, communication style, data ownership, and resilience patterns.

Frequently Asked Questions about microservices-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a monolith into microservices with clear service boundaries?▼

Split a monolith by defining service boundaries according to business capabilities or domains, ensuring each microservice owns its specific database for decentralized data management.

What is the best way to handle distributed data management in microservices?▼

Handle distributed data management in microservices by applying saga coordination and event-driven messaging to maintain data consistency across independently owned service databases.

How do circuit breakers and retries improve microservices resilience?▼

Circuit breakers and retries improve microservices resilience by preventing cascading failures during outages and isolating faults through bulkheads to maintain reliable inter-service communication.

When should I use event-driven architecture versus REST or gRPC for microservices?▼

Use event-driven architecture for asynchronous, decoupled microservices workflows, while REST or gRPC suits synchronous inter-service communication when immediate responses are required across distributed systems.

Can I use this to design an e-commerce backend with separate order and payment services?▼

Yes, you can design an e-commerce backend with separate order, payment, and inventory services by defining bounded contexts, communication styles, and fault-tolerant distributed workflows.

Related Skills

Explore More Software Engineering Skills→
chavangorakh1999chavangorakh1999
1

service-decomposition

Identify business capabilities and bounded contexts for decomposing monoliths into microservices.

Community
Advanced
NickCrewNickCrew
29

microservices-patterns

Designs microservices architectures including decomposition, communication patterns, and data ownership.

Community
Advanced
CybLowCybLow
1

arch-microservices

Design microservices with Saga orchestration, circuit breaker resilience, and 12-Factor practices.

Community
Advanced
AratKruglikAratKruglik
150

ddd-strategic-design

Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language.

Community
Advanced