microservices-architect

Design distributed systems with service boundaries and microservices patterns.

98|25|Updated Mar 14, 2020

Search Tags:#architecture #microservices #ddd #observability #service-mesh #saga #event-sourcing

Ready to run

npx skills add https://github.com/baotoq/micro-commerce --skill microservices-architect-baotoq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: microservices-architect
Source: https://github.com/baotoq/micro-commerce/tree/main/.agents/skills/microservices-architect
Command: npx skills add https://github.com/baotoq/micro-commerce --skill microservices-architect-baotoq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps software architects design and reason about distributed systems with clear service boundaries, robust patterns for decomposition, and comprehensive observability.

Core Features & Use Cases

Boundaries & Domain-Driven Design: identify bounded contexts and map relationships across complex product ecosystems.
Pattern Guidance: saga orchestration, event sourcing, CQRS, service mesh, and distributed tracing integration for cloud-native deployments.
Practical Architecture Planning: generate decomposition plans with per-service data ownership, deployment strategies, and governance.

Quick Start

Create a bounded-context decomposition plan for a monolith, detailing service boundaries, data ownership, and observability requirements.

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 service boundaries?▼

To decompose a monolith into microservices, identify bounded contexts to map domain relationships, then generate a decomposition plan defining per-service data ownership and deployment strategies.

What is the best way to manage distributed transactions across microservices?▼

Manage distributed transactions across microservices using saga orchestration. This pattern coordinates multi-step transactions across services, ensuring data consistency without requiring a monolithic shared database.

When do I need event sourcing and CQRS in a microservices architecture?▼

You need event sourcing and CQRS in a microservices architecture when building systems requiring robust audit trails and complex domain models. These patterns separate write and read operations to optimize data flow.

Does this approach support service mesh and distributed tracing for cloud-native deployments?▼

Yes, this approach supports service mesh and distributed tracing for cloud-native deployments. It defines observability requirements to integrate these technologies, enabling traffic management and request tracking across services.

Can I use domain-driven design to map bounded contexts across a complex product ecosystem?▼

Yes, you can use domain-driven design to map bounded contexts across a complex product ecosystem. It identifies core domains and their relationships, establishing clear boundaries for per-service data ownership.

What are the limitations of decomposing systems with per-service data ownership?▼

A limitation of per-service data ownership is increased architectural complexity. Decomposing systems requires robust observability, distributed tracing, and saga orchestration to manage eventual consistency across isolated databases.