skills.rest
AI-Foundry-Core
AI-Foundry-CoreOFFICIAL
Explore all skills by this author →
GitHub

microservices-patterns

Decompose monoliths into microservices with defined boundaries and contracts.

4|Updated Mar 3, 2026
Search Tags:#architecture#microservices#patterns#resilience#event-driven#distributed-systems
One-click install
npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill microservices-patterns-ai-foundry-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-patterns
Source: https://github.com/AI-Foundry-Core/ril-agents/tree/main/plugins/backend-development/skills/microservices-patterns
Command: npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill microservices-patterns-ai-foundry-core

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Microservices patterns provide a blueprint for decomposing monoliths, defining service boundaries, and implementing robust, scalable distributed systems with clear contracts and resilient communication.

Core Features & Use Cases

  • Service decomposition strategies (by business capability and DDD bounded contexts) to enable independent deployment and ownership.
  • Synchronous and asynchronous communication patterns (REST, gRPC, Kafka, Pub/Sub) to balance latency and reliability.
  • Data management and transaction handling (Database per service, Saga pattern with compensations) for eventual consistency and reliability.
  • Resilience and reliability patterns (Circuit breakers, retries with backoff, bulkheads) with practical templates and code references.
  • Saga orchestration and event-driven coordination across multiple services with rollback/compensation.
  • Reference templates and samples for API gateways, event buses, and resilience primitives.

Quick Start

Create a new microservice for the Order domain using the patterns described to define service boundaries and enable resilient communication.

Frequently Asked Questions about microservices-patterns

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

FAQPage Schema
How do I decompose a monolith into bounded microservices?▼

Implement microservices communication using synchronous patterns like REST and gRPC, or asynchronous patterns like Kafka and Pub/Sub. Choose based on your latency and reliability requirements to balance event-driven workflows with direct service calls.

How does the saga pattern handle distributed transactions and rollbacks?▼

The saga pattern handles distributed transactions through orchestration and compensating actions across multiple services. It replaces traditional distributed locks with eventual consistency, executing rollback events to reliably reverse partial transaction failures in event-driven architectures.

What resilience patterns should I apply to prevent cascading microservice failures?▼

Apply resilience patterns like circuit breakers, bulkheads, and retries with backoff to prevent cascading microservice failures. These primitives isolate faulty services, manage resource pools, and handle transient network errors in distributed systems.

Can I use an API gateway strategy for microservices with per-service database ownership?▼

Yes, API gateway strategies work with per-service database ownership by routing external requests to the correct bounded service. This setup maintains independent data stores while providing a unified entry point for versioned contracts and client communication.

Related Skills

Explore More Software Engineering Skills→
crgarcia12crgarcia12

ddd-modeling

Transform product specifications into DDD domain models with Mermaid diagrams.

Community
Advanced
ccfccf

microservices-patterns

Design microservices architectures with service boundaries and Saga patterns.

Community
Advanced
ssmleossmleo

govfolio-schema-contracts

Manage and verify domain schemas and OpenAPI contract boundaries for API services.

Community
Intermediate
proyecto26proyecto26
42

service-decomposition

Evaluate monolithic, modular monolith, and microservice trade-offs for distributed systems.

Official
Advanced