5 stages of event-driven architecture with Kafka

The journey from early-stage exploration to a fully integrated, secure, organization-wide Kafka is complex and potentially high- risk for enterprise organizations.

Get the whitepaper

This app is protected by reCAPTCHA.

Quick summary

 Few organisations plan their way to enterprise-wide Kafka. It usually starts with one team experimenting, spreads to a shared cluster, and before long Kafka is a central part of how the business exchanges data. Each step brings new challenges, and they get harder to fix the further you go.This ebook maps the five stages of event streaming maturity, from incidental use to Kafka everywhere. It covers what changes at each stage and how to get past the challenges enterprises typically face along the way.

‍

‍What you’ll learn:

  • The five stages (incidental, brokered, centralised, advanced and pervasive), so you can see where your organisation stands today
  • How Apache Kafka compares with Amazon Kinesis, Azure Event Hubs, Google Pub/Sub, Pulsar, IBM MQ, Solace and Tibco
  • Why out-of-the-box Kafka falls short once it becomes central: governance, security, self-service and day-2 maintenance
  • What data owners, architects, developers and operators each need from a shared streaming platform
  • Why the biggest challenges at the later stages are organisational rather than technical
  • How Rabobank saves €500,000 a year on Kafka maintenance, and what Stedin and Eneco achieved

"By having access to this real-time data, Eneco can use its data flexibly to help the organization and its customers even better."

Iem Smid
Go to case study

"Data governance is critical at Rabobank. With Axual, we are able to see who has permission, who owns the data, or if the owner has given permission, and what the structure of the messages are."

Vincent Oostindie
Go to case study

“We were at a crossroads, with legacy technology preventing a solid digital transformation, and an ambitious strategy for customer centricity underlining requirements for becoming data-driven. We really needed the Axual platform to allow us to make the leap.”

Roger Stoffers
Go to case study