Five years ago, a handful of our clients set out to start their event-driven journey on Confluent Kafka. Their goal: to get the right information to the right places at the right time. This had been challenging for them as they had created a complex web of integrations during the course of many years.

Like any architecture journey, the future was bright, and they found that it was straightforward to implement simple use cases. As the use cases became more complex, failures and delays plagued the process. Enthusiasm for the new architecture waned, and they fell back into their old habits of designing and implementing systems as they have been for the last 30 years.

Before long, the promising future they had envisioned was forgotten. Nobody wanted to use Kafka because it took too much time to develop new use cases and the value of being event-driven was lost. Years into this journey, they had lost their way.

Join us as we relive the highs and lows of this journey. We’ll discuss where we went wrong, the pitfalls, and how getting back to basics and thinking in terms of business architecture, capabilities, and processes helped our clients find their way again.