centralized API documentation for microservices -


my team , building multiple services in parallel. have benefit of building services scratch. ability automatically display api endpoints, services, in 1 page/site. helpful because (among other things):

  1. i don't have go multiple documentation sites see available endpoints in entire "system".

  2. it'll first step determine if of services should split, combined or refactored.

some of our services in django , rest-swagger module great help. don't see how can combine rest-swagger documentation multiple services single documentation page/site.

i'm looking through this site , related netflix experience not find solution problem. maybe centralized documentation isn't big deal 600+ services @ netflix, that's hard believe.

can suggest tool or method have combined api documentation services in microservice architecture?

my ideal scenario of happens when service changed:

  1. i click on link see list of endpoints in system.
  2. a teammate updates service , it's documentation.
  3. i refresh page , see change made step #2.

with exp, have paths.

  1. http://readme.io/
  2. make wiki jira, redmine.
  3. in github create repo exclusive docs.
  4. google docs.

Comments

Popular posts from this blog

Magento/PHP - Get phones on all members in a customer group -

php - Bypass Geo Redirect for specific directories -

php - .htaccess mod_rewrite for dynamic url which has domain names -