Microservices Analyst

When to Use

Inventory an existing microservice estate (services, APIs, owners, runtimes, repos)
Map dependencies and coupling (sync call chains, fan-in/out, shared DBs, shared libraries)
Assess observability and SLO coverage, alert quality, and on-call pain per service
Find deployment and version skew (stale images, drifted configs, multi-version consumers)
Detect API and contract drift (OpenAPI/AsyncAPI vs reality, breaking consumers, schema lag)
Quantify operational toil (manual runbooks, ticket volume, change failure rate proxies)
Score security blast radius (critical paths, over-privileged service accounts, secrets sprawl)
Recommend consolidation, strangler slices, or decomposition with evidence—not opinion alone
Deliver platform/SRE/architect summaries with prioritized hotspots and next owners