skills.rest
iCesofT
iCesofTCOMMUNITY
Explore all skills by this author →
Website𝕏@fjahijadoGitHub

microservices-patterns

Design microservices architectures with decomposition, communication, and resilience patterns.

1|1|Updated Apr 16, 2026
Search Tags:#architecture#microservices#patterns#resilience#event-driven#circuit-breaker#service-decomposition
One-click install
npx skills add https://github.com/iCesofT/awesome-ai --skill microservices-patterns-icesoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/iCesofT/awesome-ai/tree/main/agents/skills/microservices-patterns
Command: npx skills add https://github.com/iCesofT/awesome-ai --skill microservices-patterns-icesoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Microservices Architecture patterns solve the complexity of building distributed systems by providing structured approaches for decomposing monoliths, defining clear service boundaries, and establishing robust communication and resilience mechanisms.

Core Features & Use Cases

  • Service decomposition strategies (by business capability, by subdomain, strangler fig)
  • API gateway design and resilient inter-service communication
  • Event-driven communication, domain events, and saga-based distributed transactions
  • Data ownership, storage boundaries, and per-service databases guidance
  • Resilience patterns (circuit breakers, retries, bulkheads) and observability best practices

Quick Start

Identify domain boundaries for each service and map them to bounded contexts, then implement using the included patterns and templates.

Frequently Asked Questions about microservices-patterns

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

FAQPage Schema
What is the best way to decompose a monolith into microservices?▼

Event-driven communication in microservices uses domain events and saga-based coordination to manage distributed transactions, ensuring data consistency across services without relying on two-phase commits.

How do I handle distributed transactions across microservices?▼

Distributed transactions in microservices are handled using saga coordination and event-driven messaging, which provide reliable rollback and recovery mechanisms across bounded service contexts.

What resilience patterns should I implement for inter-service communication?▼

Per-service databases enforce strict data ownership in microservices by ensuring each service manages its own storage boundaries, preventing direct cross-service database access and maintaining loose coupling.

Can I use an API gateway for inter-service communication in microservices?▼

Yes, API gateway design in microservices provides a centralized entry point for routing external requests, enforcing security policies, and abstracting internal inter-service communication from clients.

When should I not use microservices architecture?▼

Microservices architecture may not suit small teams or simple domains, as the overhead of distributed systems governance, inter-service communication, and per-service databases outweighs the benefits of service decomposition.

Related Skills

Explore More Software Engineering Skills→
shafibabarshafibabar
1

bounded-context-mapping

Identify and document Bounded Contexts using Linguistic Fracture Line analysis.

Community
Advanced
ChatAndBuildChatAndBuild
1

template-governance

Manage reusable infrastructure template lifecycles with versioning and governance policies.

Official
Advanced
camoneartcamoneart
5

microservices-patterns

Design microservice boundaries, contracts, and inter-service communication patterns for distributed systems.

Community
Advanced
KentoShimizuKentoShimizu
7

architecture-monolith

Define modular monolith module boundaries and contracts within a single deployable unit.

Community
Advanced