Trilateral API per container

In the Trilateral API pattern in Chapter 3, Foundation Patterns, we talked about how a cloud-native component can publish up to three different interfaces: a synchronous API for processing commands and queries, an asynchronous API for publishing events as the state of the component changes, and an asynchronous API for consuming the events emitted by other components. The synchronous API is usually published via the API Gateway pattern, as discussed in Chapter 4, Boundary Patterns. The asynchronous API for consuming events is usually implemented as a stream consumer, as discussed in the Event Streaming pattern and the asynchronous API for publishing events is usually implemented as a database stream consumer following the Database-First variant of the Event Sourcing pattern, as discussed in Chapter 3, Foundation Patterns. This means that a cloud-native...