# Design Resilient Microservices Systems

Distributed systems create difficult decisions about boundaries, communication, data, and failure handling. This skill turns those decisions into concrete architecture and migration guidance.

## Install

```bash
npx skillstore add sickn33/microservices-patterns
```

## Metadata

- Status: approved
- Slug: sickn33-microservices-patterns
- Skillstore revision: r2
- Version status: missing
- Tree hash: 25afdc17781d7050c49526455d1e3b0e8b12857aaaf75a98ccf1194c78a4eed4
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/microservices-patterns
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-microservices-patterns
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-microservices-patterns/manifest

## Capabilities

- Identifies service boundaries using business capabilities, subdomains, and bounded contexts.
- Compares synchronous APIs with event streams, queues, and publish-subscribe communication.
- Designs database ownership, eventual consistency, sagas, and compensating actions.
- Applies API gateways, retries, timeouts, circuit breakers, and bulkheads.
- Produces migration steps, observability needs, deployment considerations, and operational guardrails.

## Use Cases

- Decompose a Monolith: Map business capabilities, data ownership, dependencies, and migration stages before extracting services.
- Design Service Communication: Choose APIs or events and define contracts, retries, timeouts, and failure handling.
- Plan Operational Resilience: Define circuit breakers, health checks, tracing, service discovery, and deployment guardrails.

## Prompt Templates

### Choose an Architecture

```
Assess whether [system] needs microservices or a modular monolith. Consider team size, scale, domain complexity, and operational support.
```

### Define Service Boundaries

```
Decompose [application] by business capability and bounded context. List each service, its responsibilities, owned data, APIs, events, and dependencies.
```

### Design a Distributed Workflow

```
Design the [workflow] across [services]. Compare orchestration and choreography, then define events, idempotency, failure handling, and compensating actions.
```

### Create a Migration Plan

```
Create a staged strangler migration for [monolith]. Include routing changes, data migration, compatibility, observability, rollback criteria, risks, and acceptance checks.
```

## Limitations

- The code samples are illustrative and omit some dependencies, types, authentication, and production configuration.
- The skill does not measure workloads, costs, latency, or organizational readiness.
- Recommendations require validation against your infrastructure, compliance rules, and failure modes.
- The skill provides guidance but does not deploy services or run operational tests.

## Best Practices

- Align each service with a business capability and assign clear data ownership.
- Design every remote call for timeouts, partial failure, retries, and observability.
- Migrate incrementally with measurable acceptance criteria and tested rollback paths.

## Anti Patterns

- Do not create services that share databases or require coordinated releases.
- Do not use synchronous calls for every interaction when events fit the workflow.
- Do not adopt microservices without operational ownership, monitoring, and deployment automation.

## Security Audit

- Audited at: 2026-08-04T14:07:29.305\+00:00
- Summary: All 11 static alerts are false positives. Network alerts identify illustrative internal service examples, while other alerts arise from business identifiers and Markdown formatting.

## Stats

- Views: 110
- Downloads: 10
- Favorites: 0
- Popularity score: 0