The Evolution of Distributed Systems on Kubernetes

Tell us a little bit about yourself and what you are currently working on.

I currently work for Red Hat as a Product Manager. I look after Data Integration and how data integration might look like in a cloud native world. Everything is moving on Kubernetes and OpenShift including data. I look after projects such as Debezium for Change Data Capture, Data Virtualization and helping drive the roadmap.

What are the goals of your talk?

Throughout the talk, we will look at what are the needs of distributed systems, what are the main features you would expect from a distributed system platform and how such platforms have evolved starting from monolithic architectures like SOA and ESB, how that changed during the Kubernetes and microservices era. And more recently, what are the latest developments in the different areas of cloud native? Our goal is to try to see where these developments may be taking us. What might be the next architecture after microservices, whether that's serverless or something else? The goal is to try to find an answer for this.

Can you give us a preview of what, in your opinion, is coming after microservices?

Many are convinced it's serverless. I'm not entirely sure. In my opinion serverless is there to stay, but probably for more specific use cases when implementing an application as a single operation makes sense. In my view, probably what's coming after microservices is decoupling more infrastructure concerns from microservices. We end up with what's called multi-runtime microservices. Your microservices composed of your business logic as a process and everything else as a sidecar, and that includes management of state, networking, binding lifecycle, many more things that still reside within a single microservice.

What do you want people to leave the talk with?

I would like people to leave with my Twitter handle probably because in the end it's a short talk and probably we will not have a definite answer, but more questions. The goal is really to make the audience think about all of these changes that are happening in the industry and for them to question when they are making technology decisions or trying to see what's the architecture that will live many years. How to look into such questions? The goal is really having an audience asking questions, and we'll talk about these.