micro-services

Decompose a monolith into bounded microservices with API contracts.

1|1|Updated Mar 26, 2026

Search Tags:#architecture #microservices #observability #cqrs #api-gateway #event-sourcing #inter-service-communication

Ready to run

npx skills add https://github.com/PedroHBO/opencode-config-skills --skill micro-services

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: micro-services
Source: https://github.com/PedroHBO/opencode-config-skills/tree/main/skills/micro-services
Command: npx skills add https://github.com/PedroHBO/opencode-config-skills --skill micro-services

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Helps teams design and implement scalable, resilient microservices architectures by guiding decomposition, communication patterns, observability, and deployment best practices.

Core Features & Use Cases

Service Decomposition: identify bounded contexts and determine service boundaries to minimize coupling.
Inter-service Communication: describe synchronous REST/gRPC and asynchronous messaging patterns and their trade-offs.
Observability & Resilience: provide tracing, logging, metrics, circuit breakers, retries, and health checks.
OpenCode Usage & Templates: provide practical examples, artefacts, and deployment checklists.

Quick Start

Create a high-level microservices plan that decomposes a monolith into bounded services with an initial API gateway configuration.

Frequently Asked Questions about micro-services

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

FAQPage Schema

How do I decompose a monolith into well-bounded microservices?▼

Microservices decomposition starts with identifying domain-driven bounded contexts to establish clear data ownership and API contracts, minimizing service coupling. This Skill guides you through determining service boundaries and generating a high-level decomposition plan.

What is the best way to handle inter-service communication in a microservices architecture?▼

Inter-service communication requires choosing between synchronous REST/gRPC and asynchronous messaging patterns based on your trade-offs. This Skill provides templates and patterns to help you implement resilient communication strategies across cloud environments.

How do I implement observability and resilience for microservices?▼

Microservices observability and resilience rely on implementing distributed tracing, logging, metrics, circuit breakers, and health checks. This Skill supplies patterns and deployment checklists to satisfy requirements for tracing and governance.

When should I use event sourcing and CQRS in microservices design?▼

Event sourcing and CQRS are applicable when designing domain-driven microservices that require resilient systems with clear data ownership. This Skill applies these patterns to establish bounded contexts and asynchronous communication topologies.

Do I need an API gateway for my microservices architecture?▼

An API gateway is needed to manage routing and configuration for your microservices architecture. This Skill helps you create an initial API gateway configuration as part of a high-level microservices plan.

What are the trade-offs between synchronous and asynchronous microservices communication?▼

Synchronous REST/gRPC communication offers immediate consistency, while asynchronous messaging decouples services for better resilience. This Skill describes the trade-offs of each pattern to guide your inter-service communication decisions.