With projects springing up at a dizzying pace, it’s hard not to feel like you’re falling behind the curve, or that you’re somehow not doing cloud native development correctly. Breaking out of this “container shame spiral” can be tough. It starts with being better equipped to evaluate projects and trends, and make better decisions about when is the right time to start adopting a new project. Otherwise, you’re all bound to stay stuck in a spiral of reacting to every new announcement. Guiding you through the last few years of container fervor, Laura will help you understand the current landscape and emerging trends, and introduce you to a framework that will help you make sense of all the rapid innovation happening around you.
5. If you truly loved pizza, you would use Pizza Scissor.
If you’re not using Pizza Scissor, you don’t love pizza.
Your tools are bad and you should feel bad!
6.
7. As an industry, we’ve
become obsessed and
dogmatic with tools.
10. Or worse — our colleagues,
peers, and customers.
11.
12. THE CONTAINER SHAME SPIRAL
Feeling worthless, ashamed, or incompetent
because your adoption of containers or
container tools is behind what you perceive
your peers to be doing.
13. We are convinced that others are exceeding our
performance. It’s impossible to catch up, and we get
stuck in a shame spiral.
Everything evolves at a cosmic pace, and it’s hard
to know what to pay attention to. The landscape is
overwhelming.
14. Take a critical look at data, and what research shows
about Cloud Native adoption.
Understand market patterns and problems to make
better choices about what to invest in and pay
attention to.
15. All companies, in all countries, in every
industry, are already using Kubernetes.
Since we’re not, we’re obviously doing
Something Wrong™
F O M O & I M P O S T O R S Y N D R O M E
20. Available data is subject to all kinds of biases.
SELECTION &
EXCLUSION
Certain groups are
more likely to be
selected for the
study,or certain
groups are kept out
by design.
REPORTING
The respondent
doesn’t report all of
the data,or skews
that data that is
reported.
FUNDING
Outcomes are
skewed to favor the
financial sponsor of
the study.
21. If uncontrolled for bias, the
data can cause us to arrive
at incorrect conclusions.
22. OPEN SURVEYS
DATA ANALYSIS
INDEPENDENT OR
ACADEMIC RESEARCH
Opt-in,self-selecting respondents,answers are self-qualified
Analysis performed on anonymized data taken from a source
No respondents,opt-out
Peer-reviewed,more stringent methodologies & theoretical models
Not necessarily tied to business goal
CNCF Survey, Digital Ocean Currents, Stack Overflow Developer Survey
Diamanti Container Adoption Benchmark Survey
DataDog Docker Adoption Report
Accelerate: State of DevOps Report
@rhein_wein
23. In addition, most of these surveys are
conducted in English only, and limited
to North America and Europe.
24. All companies, in all countries, in every
industry, are already using containers
and Kubernetes. Since we’re not, we’re
obviously doing Something Wrong™
F O M O & I M P O S T O R S Y N D R O M E
25. 25%of companies
DataDog
31%of companies in prod
State of DevOps
73%of respondents in prod
CNCF Survey
49%of respondents
Digital Ocean
12%of companies in prod
Diamanti
Who’s using containers?
Survey
Data Analysis
Independent
@rhein_wein
26. 83%of respondents
CNCF Survey
What about Kubernetes?
58%of respondents in prod
CNCF Survey
30%of companies
Diamanti
Survey
Data Analysis
Independent
No data: State of DevOps Report,DataDog
42%of respondents
Digital Ocean
@rhein_wein
28. Surveys are great for showing trends.
Without question, container
orchestration adoption is on the rise,
with Kubernetes having a large
market share.
29.
30. We use these tools because they enable
outcomes for our team and business.
Elite performers
Teams that use
cloud native practices
@rhein_wein
31. Elite performance is not dependent on a
certain tool, but on practices.
Elite performers
Teams that use
cloud native practices
32. Low change failure rate
Fast mean time to recovery (MTTR)
Cloud portability
Avoid vendor lock-in
THROUGHPUT
STABILITY
MANAGEABILITY
Frequent deployments
Low lead time from commit to deploy
Improved scalability
Faster deployment time
State of DevOps Report
CNCF Survey
Digital Ocean
34. Cloud Native is a journey toward a horizon. We’ll
never get to a point and say “Aw yeah, work is done.
No more room for improvement!”
Focus on the journey and the outcomes.
42. Developers and operators will
continue to directly interact with
only Kubernetes for all types of
applications until the end of time
Kubernetes is awesome
Kubernetes adoption is on the rise
⭐ 🌀
44. C A V E A T
Configuration-as-code is a
best practice that will be
around for a long time!
Some people are only talking about declarative services when they
say “everything will be a Kubernetes app!” I agree with them.
45. In the future, all applications will
exclusively use $tool.
I N N O V A T I O N S T O P S N O W !
46. A Framework for Evaluation
Genesis Custom Built Product Commodity
Visible (Lots of Management) Invisible (No Management)
47. Genesis Custom Built Product Commodity
Wardley Maps (simplified)
Time
InvisibleVisible
48. Genesis Custom Built Product Commodity
InvisibleVisible
Electricity
18th Century
Electricity
19th Century
Electricity
now
54. C O M M O D I T I Z AT I O N
If you have a hand-rolled solution for
running apps with containers, it’s safe to
migrate to an orchestration platform.
55. I N N OVAT I O N
Solutions to old problems get
commoditized, but it leaves room
for genesis elsewhere
56. ?
?
?
Service Mesh
Functions as a Service
Storage!
Genesis Custom Built Product Commodity
InvisibleVisible
Container
Orchestrator
Container Runtime
57. If you’re packaging and running applications, use containers.
Remember that orchestrators, container runtimes,
and other tools don’t pay your bills. Customers do.
Don’t lose sight of the outcomes you want to achieve.
If you use containers, think about the best way to manage
them. You will likely benefit from an orchestrator.