Closed Nagelfar closed 1 year ago
Currently an backend API exists with these main entry points and sub-routes (currently only documented as part of the routing configuration):
api/domains
for accessing domainsapi/boundedContexts
exposes bounded contexts and provides a basic search functionality (currently documented by these tests)api/collaborations
exposes the collaborations between bounded contexts or domainsapi/namespaces/templates
exposes the defined templates for namespacesThese endpoints could be extended into a more REST-full API containing REL-links and possible actions for resources.
In some situation you want to use data gathered in Contexture in 3rd party tools.
E.g. you want to verify & apply names of domains / bounded contexts to 'labels' of tools. (E.g. in monitoring tools attach a label named after the bounded-context to the log. In Kubernetes name a namespace after a domain;)
Potential API endpoints: