Johnny Mirza, Confluent, Senior Solutions Engineer Apache Kafka has become the de facto standard for microservice architectures. It goes far beyond reliable and scalable high-volume messaging. Developers are now moving away from non-scalable technologies like REST / HTTP.. to the distributed storage Kafka model allowing high availability and real decoupling between the independent microservices. In addition to leveraging Kafka Connect for integration and the Kafka Streams API for building lightweight stream processing microservices in autonomous teams. A Service Mesh on the other hand complements the Kafka architecture. It describes the network of microservices that make up such applications and the interactions between them. Its requirements can include discovery, load balancing, failure recovery, metrics, and monitoring. A service mesh also often has more complex operational requirements, like A/B testing, canary rollouts, rate limiting, access control, and end-to-end authentication. Let’s explore the problem of distributed Microservices communication and how both Apache Kafka and Service Mesh solutions address it. https://www.meetup.com/KafkaMelbourne/events/276036863/

1. Kafka in the Service Mesh
- Not just API’s in disguise!
Johnny Mirza

19. Thank You