Far from a controversial choice, Apache Kafka is now a technology that developers and architects are adopting with enthusiasm. This technology is enabling meaningful improvements in complex, evolvable systems that need to respond to the world in real-time.
In this talk, we’ll look at common mistakes in event-driven systems built on top of Apache Kafka:
· Deploying Kafka when an event-driven architecture is not the best choice.
· Ignoring schema management. Events are the APIs of event-driven systems!
· Writing bespoke consumers when stream processing is a better fit.
· Using stream processing when you really need a database.
· Trivializing the task of elastic scaling in all parts of the system.
It’s highly likely for medium- and large-scale systems that an event-first perspective is the most helpful one to take, but it’s early days, and it’s still possible to get this wrong. Come to this talk for a survey of mistakes not to make.