DEV · On-demand microservices

Individual revenue stream · Generated API · Imperium microservice This page lists everything the Leumas graph records about how it relates to the rest of the system.

What DEV · On-demand microservices is

Individual revenue stream · Generated API · Imperium microservice It is recorded in the Leumas graph as a revenue in the architecture grain.

What DEV · On-demand microservices relates to

The graph records 3 relationships for it, across 2 kinds. It contains Generated API and Imperium microservice.

What it depends on, and what depends on it

Nothing is recorded as a dependency of DEV · On-demand microservices. Nothing is recorded as depending on it, which for a leaf is normal and for a shared unit is worth checking.

How to read this

Every relationship here is one of nine shared kinds, mapped from the source graph rather than invented. A kind that a source uses and this model does not express is dropped and counted rather than turned into "related to", so what you see understates the source rather than embellishing it.

Questions

What does DEV · On-demand microservices depend on?

This graph records no dependencies for DEV · On-demand microservices.

What uses DEV · On-demand microservices?

Nothing in this graph is recorded as depending on DEV · On-demand microservices.