Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

microservices-architect

Designs microservice boundaries, communication patterns, data ownership, and resilience strategies for a distributed system.

When to use it

You have a monolith or a rough service list and still need clear bounded contexts, data ownership, and failure handling before splitting it up.

For example

You say

Use microservices-architect to split our Rails monolith (orders, inventory, billing, notifications) into services and show how order placement should flow.

You get
  • Service boundary diagram
  • Order placement saga design
  • Resilience plan per integration

How it works

  • Applies domain-driven design checkpoints so each service owns its data and deploys independently.
  • Chooses async messaging for long-running or cross-aggregate steps and reserves sync calls for fast queries.
  • Requires correlation IDs and end-to-end tracing across every service.