Reduce toil and complexity when developing on Kubernetes

with the right architecture

I'm passionate about cloud-native technologies, Developer Platforms, Kubernetes and multi-cloud.

 

 

move blazingly fast

"Move fast and break things. Unless you are breaking stuff, you are not moving fast enough."

- Mark Zuckerberg Meta

 

BUT...

"Moving fast and breaking things is great, unless the thing you break is your own neck."

— Reality

Systems are more complex

“As the complexity of a system increases, the accuracy of any single agent's own model of that system decreases rapidly.”

 

- Dr. David Woods

Kubernetes complexity example

Kubernetes complexity example

Architecture should reduce toil

SIMPLIFY DEVELOPMENT

Make development simpler via automation and ease of change.

STANDARDIZE

INNOVATE

Based on standards that help innovation.

SELF SERVICE

No friction, automated self service.

PLATFORM SERVICES

Consume platform level serivces

Resources

Architecture to reduce Kubernetes complexity

By Piotr

Made with Slides.com

Architecture to reduce Kubernetes complexity

- How much Kubernetes do developers need to know? Does “shift left “ mean means ever-expanding curriculum of tools and frameworks outside of the main focal point; software development? - How can we reconcile between developers taking full ownership of the software they create and other concerns like operations, security, and compliance still being properly addressed in a standardized way? - Support developers by creating standardized and reusable abstractions that make it easy for everyone to be successful with their tasks and increasing demands. - The emphasis here is on reusable services that the Platform/DevOps or other enabling Teams provide in form of tools, APIs, products, and contracts. The audience will learn - how to create smart abstractions over Kubernetes primitives - how to use those primitives to create stable and user-friendly contracts between development teams and enable teams

  • 278

More from Piotr