Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I work in a Rest Oriented environment. The number of endpoints is quite large and span multiple applications. The dependencies between the endpoints are large in number as well and not very well planned. Applications have cyclic dependencies amongst each other. Unfortunately, there is no central location where all the endpoints are documented and declare dependencies (the endpoints that they inturn call).

Is there a tool that will help in such dependency management. I tried searching for a tool online, but not know what such a thing would be called, I am unable to find anything.

share|improve this question

closed as off-topic by GlenH7, Dan Pichelman, MichaelT, gnat, Tulains Córdova Feb 2 '15 at 1:58

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking us to recommend a tool, library or favorite off-site resource are off-topic for Programmers as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it." – GlenH7, Dan Pichelman, Community, gnat, Tulains Córdova
If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 0 down vote accepted

My own search, via "service dependency discovery", yields a very few select results. IEEE give a couple of hits to papers that talk about SOA service dependency discovery, and perhaps you can use or adapt the described technique to fit your purpose. Aside from that...

IBM Tivoli and a yet to be released Microsoft Orion sound by their descriptions to be up that alley, if not a bit heavyweight for what you are probably looking for. They look to be targeted to network management for operational concerns. These, it appears, work off live network packet inspection.

Perhaps as a kludge, analyzing and aggregating service or host log files, you might have some opportunity to 'discover' who wants and needs what without digging into the guts of each through the respective sources or various project and deployment descriptors. Of course this presumes that the logging level of each service feels it is important enough to log those cross service requests and the log level isn't filtering those info events out of the log.

To fully understand the breadth and depth of each dependency, you'll probably need to delve into the service source.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.