We now live in a world with data at its heart. The amount of data being produced every day is growing exponentially and a large amount of this data is in the form of events. Whether it be updates from sensors, clicks on a website or even tweets, applications are bombarded with a never-ending stream of new events. So, how can we architect our applications to be more reactive and resilient to these fluctuating loads and better manage our thirst for data? In this session explore how Kafka and Reactive application architecture can be combined in applications to better handle our modern data needs.
Outline:
The need for event-driven architecture with example
Correcting the incorrect assumption that using Kakfa give you complete Reactivity and what this really means (i.e. reactive programming, reactive architecture, reactive manifesto)
How to configure Kafka to best enable the cornerstones of the reactive manifesto (with analogies to original example)
How to get started with Kafka
Reactive Kafka frameworks available
Demo application built using Kafka and Vert.x Kafka client and significant changes made when re-architecting this application
Useful resources and helpful links
Attendees do not need to have any specific knowledge or experience before attending this session. However, a basic understanding of mciroservices and kafka would be helpful.
Our session will enable attendees to get a clear understanding of what a reactive system is and how to enable Kafka based microservice applications to emmulate the behaviours this architecture style consists of (resiliency, elasticity, message-driven, responsiveness).