In a previous article, we explained how we took care of data modelling and exchange between Ebury services using Apache Avro, whilst addressing the most important things to take into consideration when building robust and maintainable data models. As business grows, our internal services ecosystem evolves with it. Keeping track...
When designing any new service to be included within Ebury‘s event driven architecture, we need to define the way producers and consumers will behave. This includes describing the structure of the events being produced, in order to enable downstream consumers to read them. Kafka is used to communicate between services....
In the first part of this series, we covered a CDC example, and today we’ll work in an Event Sourcing example. Event Sourcing – Salesforce If we used the same integration with event sourcing, consumers would source directly from the application, in this example, Salesforce. This avoids coupling to BOS’s...
Sounds mysterious, right? Perhaps. As Ebury embraces a more event driven architecture, it’s important we are familiar with key patterns such as CDC and Event Sourcing and when to use them. In this first installment, we’ll go through a CDC example. What are you talking about? For the uninitiated, both of...
