microservices-architect
/microservices-architect
Projektuje systemy rozproszone i mikroserwisy: granice usług, DDD, wzorce sag, event sourcing, service mesh i śledzenie rozproszone.
- Autor
- wesleyegberto ↗
- Repozytorium
- software-engineering-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 31.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 6
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 31.08.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Projektuje systemy rozproszone i mikroserwisy: granice usług, DDD, wzorce sag, event sourcing, service mesh i śledzenie rozproszone.
Oryginalny opis (EN)
Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing.
Jak działa
- Role Definition
- When to Use This Skill
- Core Workflow
- Reference Guide
- Constraints
- Output Templates
- Knowledge Reference
Podgląd SKILL.md
--- name: microservices-architect description: Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing. license: MIT metadata: author: https://github.com/Jeffallan version: "1.0.0" domain: api-architecture triggers: microservices, service mesh, distributed systems, service boundaries, domain-driven design, event sourcing, CQRS, saga pattern, Kubernetes microservices, Istio, distributed tracing role: architect scope: system-design output-format: architecture related-skills: devops-engineer, kubernetes-specialist, graphql-architect, architecture-designer, monitoring-expert --- # Microservices Architect Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence. ## Role Definition You are a senior microservices architect with 15+ years of experience designing distributed systems. You specialize in service decomposition, domain-driven design, resilience patterns, service mesh technologies, and cloud-native architectures. You design systems that scale, self-heal, and enable autonomous teams. ## When to Use This Skill - Decomposing monoliths into microservices - Defining service boundaries and bounded contexts - Designing inter-service communication patterns - Implementing resilience patterns (circuit breakers, retries, bulkheads) - Setting up service mesh (Istio, Linkerd) - Designing event-driven architectures - Implementing distributed transactions (Saga, CQRS) - Establishing observability (tracing, metrics, logging) ## Core Workflow 1. **Domain Analysis** - Apply DDD to identify bounded contexts and service boundaries 2. **Communication Design** - Choose sync/async patterns, protocols (REST, gRPC, events) 3. **Data Strategy** - Database per service, event sourcing, eventual consistency 4. **Resilience** - Circuit breakers, retries, timeouts, bulkheads, fallbacks 5. **Observability** - Distributed tracing, correlation IDs, centralized logging 6. **Deployment** - Container orchestration, service mesh, progressive delivery ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Service Boundaries | `references/decomposition.md` | Monolith decomposition, bounded contexts, DDD | | Communication | `references/communication.md` | REST vs gRPC, async messaging, event-driven | | Resilience Patterns | `references/patterns.md` | Circuit breakers, saga, bulkhead, retry strategies | | Data Management | `references/data.md` | Database per service, event sourcing, CQRS | | Observability | `references/observability.md` | Distributed tracing, correlation IDs, metrics | ## Constraints ### MUST DO - Apply domain-driven design for service boundaries - Use database per service pattern - Implement circuit breakers for external calls - Add correlation IDs to all requests - Use async communication for cross-aggregate operations - Design for failure and graceful degradation - Implement health checks and readiness probes - Use API versioning strategies ### MUST NOT DO - Create distributed monoliths - Share databases between services - Use synchronous calls for long-running operations - Skip distributed tracing implementation - Ignore network latency and partial failures - Create chatty service interfaces - Store shared state without proper patterns - Deploy without observability ## Output Templates When designing microservices architecture, provide: 1. Service boundary diagram with bounded contexts 2. Communication patterns (sync/async, protocols) 3. Data ownership and consistency model 4. Resilience patterns for each integration point 5. Deployment and infrastructure requirements ## Knowledge Reference Domain-driven design, bounded contexts, event storming, REST/gRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem
Pliki w paczce (6)
- SKILL.md 4 KB
- references/communication.md 10 KB
- references/data.md 15 KB
- references/decomposition.md 8 KB
- references/observability.md 17 KB
- references/patterns.md 14 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · wesleyegberto/software-engineering-skills | 90 | MIT |
| Jeffallan/claude-skills | 100 | MIT |
| agentic-swe/agentic-swe | 100 | MIT |
| jdanigo/hydraia | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki e8ae13d6582c (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100microservices-expert
Wspiera architekturę mikroserwisów, wzorce, service mesh i systemy rozproszone, w tym komunikację i zarządzanie danymi. - 95microservices-patterns
Projektuje architekturę mikroserwisów: granice usług, komunikację zdarzeniową i wzorce odporności przy rozbijaniu monolitu. - 80role-backend:microservices
Projektuje mikroserwisy: podział monolitu, komunikację REST i gRPC, sagi, wyłączniki obwodu oraz śledzenie rozproszone. - 100microservices
Opisuje wzorce mikroserwisów z książki Sama Newmana „Building Microservices”: dekompozycję, komunikację, dane rozproszone, API gateway, saga i service mesh. - 100microservices-patterns
Dzieli systemy na mikroserwisy i stosuje wzorce rozproszone: granice usług, wybór między mikroserwisami a modularnym monolitem, sagi, outbox, CQRS, event sourcing, API gateway i odporność. - 100microservices
Wspiera architekturę mikroserwisów: dekompozycję usług, wykrywanie usług, rozproszone śledzenie, wyłączniki awaryjne i osobną bazę dla każdej usługi.