Building an event-driven data mesh for the asynchronous supply of price data

To replace the data storage, which has been based on a central IBM DB2 z/OS to date, a solution is being set up in the Google Cloud. Via third-party software, transactions on the DB2 are transferred to an event stream for incoming asynchronous events after the commit. For traceability within the targeted event-driven system architecture, all events are recorded in persistent event repositories. The event repositories are built and integrated with Google Cloud's own NoSQL product Firestore. Through event-driven triggers, further steps in the supply are forwarded to services in Cloud Run via various Cloud Functions. From now on, these serve as domain services and are responsible for the new persistent data storage, based on Cloud SQL. Subsequently, changes to the new persistent data model are published by another outbound event repository to an outbound asynchronous interface based on PubSub.