Implementing bi-directional synchronization

Cloud-native systems are architectured to support the continuous evolution of the system. Upstream and downstream services are designed to be pluggable. New service implementations can be added without impacting related services. Furthermore, continuous deployment and delivery necessitate the ability to run multiple versions of a service side by side and synchronize data between the different versions. The old version is simply removed when the new version is complete and the feature is flipped on. In this recipe, we will enhance the database-first variant of the Event Sourcing pattern with the latching pattern to facilitate bi-directional synchronization without causing an infinite loop of events.