# Censseo Specforge Microservices Patterns

> Microservices Patterns

- Skill: `tomevault-io/censseo-specforge-microservices-patterns` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/censseo-specforge-microservices-patterns`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/censseo-specforge-microservices-patterns/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/censseo-specforge-microservices-patterns

---


# Microservices Patterns

> Design distributed systems with proper service boundaries, communication patterns, and resilience.

## Core Principles

- **Single Responsibility**: Each service owns one business capability
- **Data Autonomy**: Each service owns its data, no shared databases
- **Loose Coupling**: Services communicate through well-defined contracts
- **Failure Isolation**: One service failure shouldn't cascade
- **Independent Deployment**: Services deploy independently

## Quick Reference

| Pattern | Purpose | When to Use |
|---------|---------|-------------|
| API Gateway | Single entry point | Multiple clients, aggregation needed |
| Circuit Breaker | Prevent cascade failures | Remote service calls |
| Saga | Distributed transactions | Multi-service business process |
| Event Sourcing | Audit trail, replay | Complex state transitions |
| CQRS | Read/write optimization | High-read or complex queries |

## Service Decomposition

**By Business Capability:**
```
├── OrderService       # Order lifecycle
├── PaymentService     # Payment processing
├── InventoryService   # Stock management
├── ShippingService    # Delivery tracking
└── NotificationService # Alerts and emails
```

**By Bounded Context (DDD):**
- Identify ubiquitous language per context
- Define context boundaries
- Map relationships between contexts

## Communication Patterns

| Style | When to Use | Examples |
|-------|-------------|----------|
| Synchronous (REST/gRPC) | Real-time response needed | User queries, validation |
| Async Events (Kafka) | Fire-and-forget, broadcast | Order placed, payment received |
| Async Request-Reply | Long operations | Report generation, batch processing |

## Critical Don'ts

- Never share databases between services
- Don't create distributed monoliths (tightly coupled services)
- Avoid synchronous chains (A→B→C→D)
- Don't skip compensating transactions in sagas
- Don't adopt microservices before team is ready

## When to Load References

- For resilience patterns: `Read references/resilience-patterns.md`
- For data patterns: `Read references/data-patterns.md`

## External Resources

- [Microservices.io Patterns](https://microservices.io/patterns/)
- [Microsoft Azure Patterns](https://learn.microsoft.com/en-us/azure/architecture/microservices/design/patterns)

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/censseo) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->