Would you actually use (or pay for) a tool that maps features to services/code across microservices?

Curious to get some real opinions here.

Imagine a tool that builds a "feature-to-service" dependency graph across your codebase(s). It helps answer things like:

  • “Which services implement this product feature?”
  • “If I change this endpoint, what features will break?”
  • “What does this service actually contribute to in the product?”
  • “What’s the blast radius of this refactor?”

It would work across multiple repos, languages, and services — using a mix of static analysis, code parsing, and LLMs to understand intent.

My questions:

  • Would you use a tool like this?
  • Would your team or org pay for it?
  • Or is this one of those “cool but no one actually needs it” kind of things?

Brutal honesty welcome. Not trying to pitch — just validating if this even solves a real pain point.

Posted Apr 8, 2025, 9:11 PM UTC

11
Loading comments…