Microservice decomposition (outbound coupling)

Full workflow

Complete guide (limitations, CI, published lens): microservice-decomposition

Why use CCE

Monolith decomposition stalls without a map of outbound dependencies — HTTP clients, gRPC stubs, service discovery. Module boundaries drawn on whiteboards miss hidden coupling through shared libraries.

CCE inventories external call sites so architects can cluster by directory and propose microservice cuts with evidence.

Example command

cce -folder . -mapper-file https://releases.stackgen.com/cce/lenses/microservice-decomposition/latest/microservice-decomposition_lenses.yaml -filter all -format json

Analysis recipe

This use case is registered as recipe microservice-decomposition — run with:

cce run -folder . -language AUTO -recipes microservice-decomposition -output microservice-decomposition.json

Published lens

https://releases.stackgen.com/cce/lenses/microservice-decomposition/latest/microservice-decomposition_lenses.yaml