You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview:

  • Currently, changes in schema are delivered via new builds of microservices that consume them
  • Tracking and testing changes via new builds takes longer

Requirements:

  1. AAI should support the ability to centrally persist and serve schema updates
  2. AAI should support the ability to centrally persist and serve custom queries updates
  3. AAI should support the ability to provide schema documents via a loosely coupled REST contract
  4. AAI should support the ability to provide the schema via flexible document formats (OXM, TOSCA etc.)
  5. AAI should support the ability to provide a list of documents stored
  6. AAI should support the ability to provide an individual document
  7. AAI should support the ability to provide associations between documents (eg. an OXM and Edgerules 
  8. AAI should support the ability to consume new schema dynamically, without downtime (eg. when distributed by SDC)
  9. AAI should support the ability to notify consumers of schema when new updates are available

Scope for Dublin:

R1-R7 

Design:

  1. A mS will load all the schema (OXM and edge rules)  at start up 
  2. A mS will load all the custom queries at start up
  3. The mS will provide REST  endpoints such as GET /aai/schema-service/v1....... following the semantic versioning guidelines
  4. The REST endpoiint support a format query parameter which will describe what format it is requested in eg. GET /aai/schema-service/v1/nodes?version={version}&format=OXM
  5. The 



  • No labels