Last time, we got familiar with the main concepts of Event Sourcing and reviewed the cons and pros of this approach. Let's see it in practice now.
Last time, we got familiar with the main concepts of Event Sourcing and reviewed the cons and pros of this approach. Let's see it in practice now.
Last time, we got familiar with the main concepts of Event Sourcing and reviewed the cons and pros of this approach. Let's see it in practice now.
In the previous blog post, I promised we would introduce something special this time. So here we go - meet almighty Dionysus, who knows how to make the most of Kafka.
In a galaxy far, far away, enter the saga of CQRS and event sourcing, where data updates unfold like an epic space opera. Jokes away, let’s see what are those.
Let's discuss how we use Kafka in Smily, how we got where we are now, and how the overall architecture has evolved over time.
Let's start with perhaps the most exciting piece of tech we use in Smily - Apache Kafka.
Let's examine the four primary ways services can be integrated and how they all play their part in our architecture in Smily (formerly BookingSync).