II.
Workflow overview
Reference · liveworkflow:microservice-decomposition
Microservice Decomposition overview
Analyzes a monolithic service to identify bounded contexts and extract them into independent microservices — modeling domain boundaries, defining API contracts, planning data ownership splits, and executing phased extraction with traffic mirroring. Excludes ongoing microservice maintenance.
Attributes
displayName
Microservice Decomposition
workflowKind
development
triggerType
on-demand
typicalCadence
per-initiative
complexity
cross-team
description
Analyzes a monolithic service to identify bounded contexts and extract
them into independent microservices — modeling domain boundaries,
defining API contracts, planning data ownership splits, and executing
phased extraction with traffic mirroring. Excludes ongoing microservice
maintenance.
Outgoing edges
applies_to_domain2
- domain:software-engineering·DomainSoftware Engineering
- domain:platform-engineering·DomainPlatform Engineering
involves_role3
- role:principal-engineer·RolePrincipal Engineer
- role:staff-engineer·RoleStaff Engineer
- role:tech-lead·RoleTech Lead
performed_by_org_unit2
- org-unit:engineering·OrgUnitEngineering
- org-unit:architecture-guild·OrgUnitArchitecture Guild
requires_skill_area3
- skill-area:domain-driven-design·SkillAreaDomain-Driven Design
- skill-area:monolith-vs-microservices·SkillAreaMonolith vs Microservices Tradeoffs
- skill-area:monorepo-extraction·SkillAreaMonorepo Extraction
triggers_responsibility2
- responsibility:approve-architecture·ResponsibilityApprove architecture proposals
- responsibility:write-rfc-documents·ResponsibilityWrite RFC / design documents
Incoming edges
follows_workflow2
- stack-profile:api-gateway-microservices·StackProfileAPI Gateway & Microservices (Kong/Envoy + gRPC + Kubernetes + Go)
- stack-profile:grpc-microservice-mesh·StackProfilegRPC Microservice Mesh Stack (Go, gRPC, Kubernetes, PostgreSQL, Prometheus)