You are viewing content from a past/completed QCon -

SESSION + Live Q&A

The Evolution of Distributed Systems on Kubernetes

Cloud native applications of the future will consist of hybrid workloads: stateful applications, batch jobs, stateless microservices, functions, (and maybe something else too) wrapped as Linux containers and deployed via Kubernetes on any cloud. Functions and the so-called serverless computing model is the latest evolution of what started as SOA years ago. But is it the last step of the application architecture evolution and is it here to stay? During this talk, we will take you on a journey exploring distributed application needs and how they evolved with Kubernetes, Istio, Knative, Dapr, and other projects. By the end of the session, you will know what is coming after microservices.


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.


Speaker

Bilgin Ibryam

Product Manager and former Architect @RedHat

Bilgin Ibryam is a product manager and a former architect at Red Hat. He is a regular blogger, open source evangelist, speaker, and the author of Camel Design Patterns and co-author of Kubernetes Patterns books. He has over a decade of experience in designing and building scalable and resilient...

Read more
Find Bilgin Ibryam at:

Location

Churchill, G flr.

Track

Kubernetes and Cloud Architectures

Topics

LondonDistributed SystemsKubernetesInterview Available

Share

From the same track

SESSION + Live Q&A Infrastructure

Lessons Learned from Reviewing 150 Infrastructures

Since April 2018 we've had the opportunity to perform a structured review of the architectural and operational choices of 150 platform teams. In this talk I'll explore some themes, talk about common mistakes, and give some advice on how to avoid these yourselves....

Jon Topper

CTO / CEO @scalefactory

SESSION + Live Q&A Serverless

A Kubernetes Operator for etcd

Etcd is a distributed key-value store, best known for being the data store used by Kubernetes itself. But what if you use etcd directly in your application, and you need it inside a Kubernetes cluster? Stateful applications, databases in particular, have traditionally posed a challenge for...

James Laverack

Solutions Engineer @JetstackHQ

SESSION + Live Q&A Kubernetes

Kubernetes is Not Your Platform, It's Just the Foundation

Kubernetes helps us tame sprawling microservices architectures and address increased operational complexity. Kubernetes gives developers abstractions and APIs to deploy and run their services. But there is a price to pay in terms of both the in-house operational expertise required and the...

Manuel Pais

IT Organizational Consultant and co-author of Team Topologies

SESSION + Live Q&A Containers

Cloud Native is About Culture, not Containers

As a developer in the IBM Garage, Holly Cummins works with customers who are trying to shift their businesses to the cloud and become more cloud native. Their dream is more effort higher up the value chain, more innovation, and greater adaptability. What’s getting in their way isn’t...

Holly Cummins

Quarkus Senior Principal Software Engineer @RedHat

View full Schedule