During this talk, Bilgin 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
Modern distributed applications
● 100s of components and 1000s of instances
● Polyglot, independent, and automatable components
● Hybrid workloads on hybrid environments
● Open source, open standards, and interoperable
● Build on the Kubernetes ecosystem
What are the needs of
● ConﬁgMaps used in Pods as:
○ environment variables
○ Minimal Node spread
○ Only stored in memory in a tmpfs
○ Encrypted in the backend store (etcd)
○ Access can be restricted with RBAC
How to extend Kubernetes?
mechanism for orthogonal
Deﬁne domain-speciﬁc knowledge in
Data plane Control plane
Service Mesh & API Gateway capabilities
● Service discovery and failover
● Dynamic trafﬁc routing
● Retry, timeout, circuit breaking
● Security, rate limiting, encryption
● Observability and tracing
What is Knative?
interactions that can
"scale to zero".
for consuming and
Kubernetes-based platform to deploy, and manage
● Better sidecars kubernetes/753
● More operators, better operators
● Data Plane Development Kit (DPDK)
● Envoy: More L7 protocols, Wasm
● Bindings move out of the application
● More resource bindings for Dapr, Knative
● More work is needed!
● There are no pluggable, polyglot
stateful abstractions for federation,
CDC, caching, idempotency, etc.