Map of external systems
What stops if a provider goes down? All of a module's outgoing connections, each with its source file and configuration key.
Transcript
After a provider outage, the first question is what stops working. This video shows how to see all of a module's outgoing connections, with evidence. The module's page holds the integration inventory.
This contract module has four connections: an Oracle database, two Kafka channels and an HTTP gateway. Each one says what it is for. The outgoing Kafka channel publishes contract lifecycle events, and names who consumes them.
And better still: every claim comes with the source file and the configuration key where the connection is defined. No need to take it on trust. So an outage impact analysis is built from the code, not from interviews.
