Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
A DevOps State of Mind with Microservices, Containers and Kubernetes
1. A DevOps State of Mind
with Microservices, Containers
and Kubernetes
Chris Van Tuin
Chief Technologist, NA West / Silicon Valley
cvantuin@redhat.com
4. $4.3 billion in unsold inventory
H&M gets hit with the ‘Amazon effect’
https://www.marketwatch.com/story/hm-gets-hit-with-the-amazon-effect-2018-04-03
10. “H&M need to make
sure they’re innovating
ahead of the curve,
not just to catch up”
H&M’s position is
magnified by the fact
that they recognized the
problem later than their
peers
H&M investing in I.T. to …
Speed
Up
Innovation
Amplify &
Shorten
Feedback Loop
13. DEV QA OPS
“THROW IT OVER THE WALL”
Challenges
1. Environment drift
2. Large change set =
more bugs, more testing
3. Extended feedback loop
Walled off people, walled off processes, walled off technologies
14. HOW DOES I.T. TRANSFORM FROM
A COST CENTER INTO AN INNOVATION CENTER?
Months
Innovation
16. DEVOPS
Speeding Up Time to Market
Leverage
tooling &
automation
Reduce
organizational
silos
Accept
failure
as normal
Implement
gradual
change
Measure
everything
17. DEV QA OPS
Linux + Containers
IaaS
Orchestration
CI/CD
Source Control Management
Collaboration
Build and Artifact Management
Testing
Frameworks
Culture Process Technology
+ +
Collaborative
Transparent
Open
Agile
Continuous
Iterative
Automate
Open Source
Hybrid
Dynamic
THE DEVOPS FACTORY
18. THE VALUE OF DEVOPS
Faster
Time to
Market
Security
More time
To
Innovate
Faster
Resolution
Of Problems
More Stable
Operating
Environment
Improved
Communication
& Collaboration
Less Complex
Less Risk
20. Collaboration Shared problems
are solved faster
+
OPEN SOURCE
CULTURE
Transparency
(both access and
the ability to act)
Working together
creates necessary
standardization
+
IT’S NOT JUST CODE; IT’S CULTURE
26. 4
● Are there known vulnerabilities in
the application layer?
● Are the runtime and OS layers up
to date?
● How frequently will the container
be updated and how will I know
when it’s updated?
CONTENT: EACH LAYER MATTERS
CONTAINER
OS
RUNTIME
APPLICATION
CONTENT: EACH LAYER MATTERS
AYER MATTERS
CONTAINER
OS
RUNTIME
APPLICATION
JAR CONTAINER
30. DEV QA OPS
Open organization +
cross-functional teams
Software factory
automation
CI/CD pipelines
with feedback
Culture Process Technology
+ +
THE DEVOPS FACTORY
44. Version 1 Version 1Version 1
Version 1.2
`
Tests / CI
RECREATE WITH DOWNTIME
45. Version 1 Version 1Version 1
Version 1.2
`
Tests / CI
RECREATE WITH DOWNTIME
46. Version 1.2 Version 1.2Version 1.2
RECREATE WITH DOWNTIME
Use Case
• Non-mission critical services
Cons
• Downtime
Pros
• Simple, clean
• No Schema incompatibilities
• No API versioning
51. Each container/pod is updated one by one
Version 1.2Version 1.2Version 1.2
100%
Use Case
• Horizontally scaled
• Backward compatible
API/data
• Microservices
Cons
• Require backward
compatible APIs/data
• Resource overhead
Pros
• Zero downtime
• Reduced risk, gradual
rollout w/health checks
• Ready for rollback
55. Version 1 Tests / CI
BLUE / GREEN DEPLOYMENT
Version 1.2
BLUE GREEN
56. Version 1 Version 1.2
BLUE / GREEN DEPLOYMENT
Route
Version 1.2
BLUE GREEN
57. Version 1
BLUE / GREEN DEPLOYMENT
Rollback
Route
Version 1.2
BLUE GREEN
Use Case
• Self-contained micro
services (data)
Cons
• Resource overhead
• Data synchronization
Pros
• Low risk, never
change production
• No downtime
• Production like testing
• Rollback
59. ”only about 1/3 of ideas improve the metrics
they were designed to improve.”
Ronny Kohavi, Microsoft (Amazon)
MICROSERVICES
RAPID INNNOVATION & EXPERIMENTATION