CtrlK
BlogDocsLog inGet started
Tessl Logo

jbvc/microservices-patterns

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

65

Quality

65%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files
name:
microservices-patterns
description:
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

Microservices Patterns

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

Use this skill when

  • Decomposing monoliths into microservices
  • Designing service boundaries and contracts
  • Implementing inter-service communication
  • Managing distributed data and transactions
  • Building resilient distributed systems
  • Implementing service discovery and load balancing
  • Designing event-driven architectures

Do not use this skill when

  • The system is small enough for a modular monolith
  • You need a quick prototype without distributed complexity
  • There is no operational support for distributed systems

Instructions

  1. Identify domain boundaries and ownership for each service.
  2. Define contracts, data ownership, and communication patterns.
  3. Plan resilience, observability, and deployment strategy.
  4. Provide migration steps and operational guardrails.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.
Workspace
jbvc
Visibility
Public
Created
Last updated
Publish Source
CLI
Badge
jbvc/microservices-patterns badge