skills.rest
dieu-donnee
dieu-donneeCOMMUNITY
Explore all skills by this author →
GitHub

microservices-architect

Design distributed system architectures and define service boundaries for monoliths.

Updated Jan 9, 2026
Search Tags:#architecture#microservices#domain-driven-design#cqrs#event-sourcing#bounded-contexts#saga-pattern
One-click install
npx skills add https://github.com/dieu-donnee/luxtrax --skill microservices-architect-dieu-donnee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-architect
Source: https://github.com/dieu-donnee/luxtrax/tree/main/.agent/skills/microservices-architect
Command: npx skills add https://github.com/dieu-donnee/luxtrax --skill microservices-architect-dieu-donnee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs scalable, resilient microservice architectures by clearly delineating bounded contexts and service boundaries to enable safe monolith decomposition.

Core Features & Use Cases

  • Domain-driven design guidance: identify bounded contexts, aggregates, and public APIs.
  • Architecture artifacts: service boundary diagrams, context maps, and resilience strategies.
  • Use Case: re-architect a monolith into independent services with clear ownership and data boundaries.

Quick Start

Sketch the first bounded-context boundaries and API contracts for a sample monolith migration.

Frequently Asked Questions about microservices-architect

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

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

Domain-driven design identifies bounded contexts and aggregates to define service boundaries for microservices. It maps domain logic to public APIs and establishes per-service data ownership, ensuring resilient distributed systems without tight coupling between services.

How does the saga pattern work for distributed transactions in microservices?▼

Saga orchestration manages distributed transactions across microservices by coordinating local operations with compensating actions. It replaces traditional monolithic database transactions, ensuring data consistency across independent services without violating bounded context boundaries.

Do I need event sourcing and CQRS for cloud-native microservice deployments?▼

Event sourcing and CQRS are not strictly required for cloud-native microservices but provide significant benefits for complex domains. They separate command and query workloads, enabling independent scaling while persisting state as an immutable event log for reliable recovery.

What's the best way to enforce resilience patterns like circuit breakers in microservices?▼

Enforcing resilience patterns like circuit breakers, retries, and bulkheads in microservices prevents cascading failures across service boundaries. These patterns isolate faults within individual bounded contexts, maintaining overall system availability during partial network outages.

When should I not use microservices for my architecture?▼

Microservices should be avoided when domain boundaries are unclear or system complexity does not justify distributed overhead. If a monolith can be effectively structured using bounded contexts without independent deployment requirements, a distributed architecture introduces unnecessary operational costs.

Related Skills

Explore More Software Engineering Skills→
LLM-Dev-OpsLLM-Dev-Ops
1

V3 DDD Architecture

Decompose monolithic orchestrators into bounded contexts with Domain-Driven Design.

Official
Advanced
woernflwoernfl

kubernetes-deployment

Automate Kubernetes deployments from containerization to cluster rollout with Helm.

Community
Advanced
JeffallanJeffallan
10.9k

microservices-architect

Decompose monoliths into microservices with domain-driven design and saga patterns.

Community
Advanced
mahg-esmahg-es
3

microservice

Define microservice boundaries with bounded contexts, data ownership, and API contracts.

Official
Advanced