Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • I think this is a good way to attack the problem if you are starting off with building with microservices, but for existing setup I am planning on parsing apache logs to get some usage information and document those, as well as have a meeting with the application owners. Commented Jan 25, 2018 at 19:55
  • @hyde Are you in a position where you can reasonably demand that the service owners each justify the existence of their service? (Supported with metrics and log data?) Or, are you the service owner? ... Do you have a centralized repository of repositories you can search those app configs for service references? Commented Jan 25, 2018 at 20:14
  • No, I am not in a position to change the way these applications are set up at this time, which I think is what you were implying by asking the service owners to justify their existence. ;) I was lucky to stumble upon JSON files in our production servers that list services and the URLs they use to reach those. While this does not provide a complete picture of the setup, I think it's a good starting point. Commented Feb 2, 2018 at 2:52
  • Umm. Not really what I was implying. But, I worded my comment very poorly ... basically, if each service owner is responsibly doing the things I listed above, each owner should be able to tell you where their service fits in and what its dependencies are (or whether it's even being used). Commented Feb 2, 2018 at 2:57
  • ... Beyond that, at the particularly large company for which I currently work, the service interactions are so complicated that it cannot be fully diagrammed. And that's OK. Each owner knows their service's dependencies and makes promises to their consumers in the combination of promising backwards compatibility (usually), mailing lists for the exceptions, and SLA's. Commented Feb 2, 2018 at 2:59