Featured

microservices-patterns

Name: microservices-patterns
Rating: 5 (20990 reviews)
Author: wshobson

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

TL;DR

Design microservices with clear boundaries, event-driven comms, and resilience patterns.

What Is It

Decompose monoliths into domain-owned services
Use event-driven communication for loose coupling
Implement circuit breakers and retries for resilience
Manage data per service to avoid shared state

Key Features

Service boundaries by business capability or subdomain
Asynchronous events for decoupled communication
Database per service to enable autonomy
Circuit breaker to prevent cascading failures
Saga pattern for distributed transactions
Bulkhead isolation to limit failure impact
API gateway for centralized routing and error handling

How to Use

1.Identify business capabilities and map to services
2.Choose synchronous or asynchronous communication based on use case
3.Apply circuit breakers and retries to services
4.Use event-driven patterns for inter-service coordination

Guardrails & Gotchas

MUST avoid shared databases across services
FORBIDDEN: do not use tight coupling between services
MUST handle failures with backoff and retries
CRITICAL: monitor service health and timeouts

GitHub Stats

Author

@wshobson

Repository

wshobson/agents

Stars

20990

Explore More Skills

move-code-quality

@davila7

Analyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working with .move files or Move.toml manifests.

12.4k

1.1k

1w ago

microservices-patterns

Explore More Skills

move-code-quality

e2e-testing-patterns

testing-anti-patterns