Harvesting information for your service registry

I was just going through some old notes from last year’s Australian Architecture Forum. One of the presenters spoke about how service registries are very useful, but often will end up out of date with the real running systems due to the maintenance overhead.  The suggestion was to harvest information from various sources, such as:

  1. version control
  2. continuous integration servers
  3. interface documentation
  4. task / issue tracking systems
  5. application servers and message broker

I’ll be looking for ways to add these to the governance toolkit, as  regardless how many rules we put in place, people will always find ways around them, often for what sounds like good reason (so they don’t tell you!)

Leave a Reply

Your email address will not be published. Required fields are marked *