As event-driven design and microservice architectures are becoming more popular, distributed systems are being seen often and becoming more complex. A once simple web server with a database is now often distributed between multiple databases, caches, services, and systems. By utilizing Apache Kafka, one can reduce the complexity of a distributed system, build fault-tolerant & scalable services, de-couple integrations between different components, and easily expand when new systems are needed.
In this presentation, I’ll go over what a distributed system is, what event-driven architecture is, how it relates to service-oriented architecture, and why we need distributed systems. I’ll give an overview of Apache Kafka, how it works, and how it relates to other message brokers. Lastly, I’ll share my experiences utilizing Apache Kafka as the backbone to build a scalable, fault-tolerant data streaming platform.
Distributed systems engineer and Apache Kafka enthusiast. At work, I'm currently architecting and implementing a data streaming platform. Outside of work, I like to write code, listen to music, and share cool tech with people.
This will add your name to the list of interested participants. It will help us gauge interest for scheduling purposes.