What is microservices-architecture?

A guide to splitting an application into small services that communicate over a network, with separate responsibilities such as users, orders, or payments.

Use it to design service boundaries, APIs, gateways, service discovery, distributed transactions, and deployment approaches.

It helps teams organize distributed applications, scale services independently, and manage communication and data consistency between them.

microservices-architecture — Skill by aj-geddes/useful-ai-prompts

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add aj-geddes/useful-ai-prompts --skill microservices-architecture

Clone the repo

git clone --depth 1 https://github.com/aj-geddes/useful-ai-prompts

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/microservices-architecture/github.svg)](https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/microservices-architecture)

Your own site

<a href="https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/microservices-architecture"><img src="https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/microservices-architecture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/microservices-architecture"><img src="https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/microservices-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 707 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 16 Sept 2026
Snyk pass 16 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.00707
Opus 5.5	$0.00018	$0.00283
Sonnet 5.5	$0.00009	$0.00141
Haiku 4.5	$0.00005	$0.00071

Measured 2mo ago against content hash fc6897f63328, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

microservices-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/validate-config.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/microservices-architecture/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Comprehensive guide to designing, implementing, and maintaining microservices architectures. Covers service decomposition, communication patterns, data management, deployment strategies, and observability for distributed systems.

When to Use

Designing new microservices architectures
Decomposing monolithic applications
Implementing service-to-service communication
Setting up API gateways and service mesh
Implementing service discovery
Managing distributed transactions
Designing inter-service data consistency
Scaling independent services

Quick Start

Minimal working example:

Bounded Contexts:
┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐
│  Order Service  │  │  User Service   │  │ Payment Service │
│                 │  │                 │  │                 │
│ - Create Order  │  │ - User Profile  │  │ - Process Pay   │
│ - Order Status  │  │ - Auth          │  │ - Refund        │
│ - Order History │  │ - Preferences   │  │ - Transactions  │
└─────────────────┘  └─────────────────┘  └─────────────────┘

Reference Guides

Detailed implementations in the references/ directory:

Guide	Contents
Service Boundary Design	Service Boundary Design
Communication Patterns	Communication Patterns
API Gateway Pattern	API Gateway Pattern
Service Discovery	Service Discovery
Data Consistency Patterns	Data Consistency Patterns
Service Mesh (Istio)	Service Mesh (Istio)

Best Practices

✅ DO

Design services around business capabilities
Use asynchronous communication where possible
Implement circuit breakers for resilience
Use API gateway for cross-cutting concerns
Implement distributed tracing
Use service mesh for service-to-service communication
Design for failure (chaos engineering)
Implement health checks for all services
Use correlation IDs for request tracking
Version your APIs
Implement proper monitoring and alerting
Use event-driven architecture for loose coupling
Implement idempotent operations
Use database per service pattern

Read the full file on GitHub · 96 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 96 lines · 46 tokens per session scan A fc6897f63328

Subscribe to this mod's changes

microservices-architecture is a skill published in the GitHub repository aj-geddes/useful-ai-prompts (376 stars, last pushed 8mo ago), licensed MIT. It adds 46 tokens to every session and 707 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Backend and APIs Cloud DevOps and cloud

microservices-architecture next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
microservices-architectureaj-geddes/useful-ai-prompts	Skill	376	8mo ago	MIT	A	46	Claude Code, Codex
stripe-projectsNousResearch/hermes-agent	Skill	261k	yesterday	MIT	A	15	Claude Code, Codex
alchemy-providerpingdotgg/t3code	Skill	48k	yesterday	MIT	A	153	Claude Code, Codex
django-storages-s3Jeffallan/claude-skills	Skill	12k	7d ago	MIT	A	138	Claude Code
websocket-engineerJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	36	Claude Code
azure-eventhub-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	94	Claude Code
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	78	Claude Code

microservices-architecture