{"enrichment":{"faq":[{"a":"microservices-patterns guides you through monolith decomposition by starting with bounded contexts\u2014identifying natural service boundaries aligned to business capabilities. The skill covers the strangler fig pattern for gradual extraction, helping you avoid the distributed monolith anti-pattern. Begin by analyzing data ownership and service responsibilities, then incrementally route traffic to new services while keeping the legacy system operational.","q":"How do I decompose a monolith into microservices?"},{"a":"microservices-patterns covers essential patterns including API gateways for routing, service discovery (client-side vs. server-side), and communication strategies (REST vs. gRPC). It addresses resilience patterns like circuit breakers and bulkheads for fault isolation, saga patterns for distributed transactions, and event-driven architectures. You'll also learn CQRS and event sourcing design tradeoffs, plus backend-for-frontend (BFF) patterns for client-specific APIs.","q":"What are the key microservices architecture patterns?"},{"a":"microservices-patterns explains saga pattern for coordinating transactions across services without distributed locks. It covers two approaches: orchestration (a central coordinator directs steps) and choreography (services react to events). The skill helps you choose between them based on complexity and observability needs, and shows how to handle compensating transactions when failures occur, keeping your system consistent without tight coupling.","q":"How does the saga pattern handle distributed transactions?"},{"a":"microservices-patterns teaches circuit breaker and bulkhead patterns to prevent cascading failures. Circuit breakers stop requests to failing services, while bulkheads isolate resources to contain damage. The skill covers when and how to apply these patterns, service mesh integration for transparent resilience, and designing for graceful degradation. These patterns keep your system stable even when individual services experience issues.","q":"What resilience patterns protect microservices from failure?"},{"a":"microservices-patterns explores CQRS (Command Query Responsibility Segregation) and event sourcing design tradeoffs. Event sourcing stores state changes as immutable events, enabling audit logs and temporal queries but adding complexity. CQRS separates read and write models for optimization. The skill helps you decide if these patterns fit your consistency, scalability, and auditability requirements, or if simpler approaches suffice.","q":"When should I use event sourcing and CQRS?"},{"a":"microservices-patterns helps you decide by weighing team structure, deployment frequency, and scaling needs against operational complexity. Monoliths suit small teams and simple domains; microservices enable independent scaling and deployment but introduce distributed system challenges. The skill teaches you to recognize when you're ready\u2014typically when bounded contexts are clear, teams are distributed, or scaling needs differ across components.","q":"Should I decompose my system or keep it as a monolith?"}],"shadow_tags":["distributed-systems","resilience-patterns","system-decomposition","eventual-consistency","service-boundaries","failure-isolation","asynchronous-messaging","data-consistency","architectural-tradeoffs","operational-complexity"],"summary_rewrite":"Master the decision to decompose systems into independent services and the patterns that keep them reliable. Covers bounded contexts, strangler fig extraction, synchronous vs. asynchronous communication, circuit breakers, saga patterns, and event sourcing\u2014helping you avoid distributed monoliths and operational chaos."},"files":[{"bytes":22343,"path":".claude/skills/microservices-patterns/SKILL.md","sha256":"24f72e312c6a4a4e92e1ec97a4f3823e8dd7e7a633aca60d544e9a46c2503dfd","url":"https://skillfed.io/files/curiositech/some_claude_skills/microservices-patterns/462794c5/SKILL.md"}],"id":"curiositech/some_claude_skills/microservices-patterns","links":{"html":"https://skillfed.io/curiositech/some_claude_skills/microservices-patterns","md":"https://skillfed.io/curiositech/some_claude_skills/microservices-patterns.md","repo":"https://github.com/curiositech/some_claude_skills"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":27,"language":"TypeScript","last_updated":"2026-07-14","license":"MIT","name":"microservices-patterns","publisher":"curiositech","stars":164},"relations":{"categories":["microservices","distributed-systems","system-design"],"similar":[{"id":"HermeticOrmus/LibreUIUX-Claude-Code/microservices-patterns"},{"id":"secondsky/claude-skills/microservices-patterns"},{"id":"pluginagentmarketplace/custom-plugin-java/java-microservices"},{"id":"Jeffallan/claude-skills/microservices-architect"},{"id":"ancoleman/ai-design-components/designing-distributed-systems"},{"id":"personamanagmentlayer/pcl/microservices-expert"},{"id":"wshobson/agents/microservices-patterns"},{"id":"finsilabs/awesome-ecommerce-skills/composable-commerce"},{"id":"eyadsibai/ltk/saga-orchestration"},{"id":"eyadsibai/ltk/microservices-patterns"}]},"slug":{"owner":"curiositech","repo":"some_claude_skills","skill":"microservices-patterns"},"version":"462794c5"}