Skip to content

Comparison of Service Mesh implement. & Architect. Caching Patterns for K8s

Photo of
Hosted By
Tereza and Dawid Z.
Comparison of Service Mesh implement. & Architect. Caching Patterns for K8s


Join us on March 24th at 6pm CET for a Kubernetes and Istio meetp.

First we have the pleasure to welcome Hanna Prinz & Jörg Müller who will talk about "Istio, Linkerd 2, or …? A comparison of Service Mesh implementations". And for the 2nd half of the evening we have Rafal Leszko talking about "Architectural Caching Patterns for Kubernetes"

  • AGENDA -

[18:00 - 18:10] - Welcome + house keeping
[18:10 - 18:50] - "Istio, Linkerd 2, or …? A comparison of Service Mesh implementations" by Hanna Prinz & Jörg Müller.
[18:50 - 19:00] - Q&A with Hanna & Jörg.
[19:00 - 19:40] - "Architectural Caching Patterns for Kubernetes", by Rafal Leszko.
[19:40 - 19:50] - Q&A with Rafal.
[19:50 - 20:00] - End of meetup.

  • TALKS -

Hanna Prinz & Jörg Müller
Istio, Linkerd 2, or …? A comparison of Service Mesh implementations

Service Meshes solve many problems of current microservice applications. They add observability, routing, resilience, and security features as a dedicated infrastructure layer. Communication between applications can be monitored, configured and secured without adding or changing application code.
For a long time, Istio was almost synonymous with the term Service Mesh. Meanwhile, many other options often remain under the radar. But how can developers find the right mesh for the project? And what are the most relevant features for that decision?
Comparing different Service Meshes is a time-consuming business. This talk aims to shorten this process. It will provide a comparison of the most relevant features and will show important implementation details. Also compatibility, usability, and performance will be discussed.


Rafael Leszko
Architectural Caching Patterns for Kubernetes

Kubernetes brings new ideas on how to organize the caching layer for your applications. You can still use the old-but-good client-server topology, but now there is much more than that. This session will start with the known distributed caching topologies: embedded, client-server, and cloud. Then, I'll present Kubernetes-only caching strategies, including:

  • Sidecar Caching
  • Reverse Proxy Caching with Nginx
  • Reverse Proxy Sidecar Caching with Hazelcast
  • Envoy-level caching with Service Mesh

In this session you'll see:

  • A walk-through of all caching topologies you can use in Kubernetes

  • Pros and Cons of each solution

  • The future of caching in container-based environments


A Consultant at INNOQ, focusing on Service Mesh and Infrastructure. Before that, she worked as a developer for backend, web and apps and as a lecturer for programming. Ever since she experienced the challenges of Ops, she has been most interested in the field of automation and DevOps like Kubernetes, CI/CD and Service Meshes.

A Principal Consultant at INNOQ. Since more than twenty years, he has been working in different roles in IT consulting and software development. Currently he focuses on architecture and operations of software as a service. Topics include Microservices, Continuous Delivery and Kubernetes. He contributes to the community by writing articles and speaking at conferences. He is also involved in the organization of the JUG Berlin-Brandenburg and several conferences.

Cloud-Native Team Lead at Hazelcast, author of the book "Continuous Delivery with Docker and Jenkins", trainer, and conference speaker. He specializes in Java development, Cloud environments, and Continuous Delivery. Former employee in a number of companies and scientific organizations: Google, CERN, AGH University, and more. Website:

Online event
This event has passed