Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
85
78%
Does it follow best practices?
Impact
96%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/microservices-patterns/skills/microservices-patterns/SKILL.mdResilient HTTP service client
Uses httpx
0%
50%
Connection timeout
0%
100%
Read timeout
25%
100%
Uses tenacity
100%
100%
Retry attempts
100%
100%
Exponential backoff multiplier
100%
100%
Backoff min/max
50%
100%
Circuit breaker failure threshold
100%
100%
Circuit breaker recovery timeout
100%
100%
Three CB states
100%
100%
Fail fast when OPEN
100%
100%
HALF_OPEN transition
100%
100%
Reset on success
100%
100%
Event-driven saga with compensation
Uses aiokafka
100%
100%
Kafka producer publish
100%
100%
Domain events published
100%
100%
Async throughout
100%
100%
Saga step structure
100%
100%
Compensation on failure
100%
100%
Reverse compensation order
100%
100%
Failure result returned
100%
100%
Async preferred over sync
100%
100%
Compensation explanation
50%
100%
Kafka library named
100%
100%
Strangler fig decomposition and API gateway
Strangler Fig named
100%
100%
Proxy routing described
100%
100%
Proxy routes old and new
100%
100%
Business capability decomposition
100%
100%
Database per service
100%
100%
No shared DB in code
100%
100%
asyncio.gather in gateway
100%
100%
Partial failure handling
100%
100%
Uses FastAPI
0%
0%
Uses httpx in gateway
0%
100%
Async gateway methods
100%
100%
Incremental migration
100%
100%
90d6bd7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.