In this talk I point out several areas of focus when making the transition to a DevOps culture, and point out why it’s important that you change everything.

1. @kmugrage@kmugrage
“YOU BUILD IT, YOU RUN IT”
–Werner Vogels, Amazon

2. @kmugrage@kmugrage
“…IT ALSO BRINGS THEM INTO DAY-TO-
DAY CONTACT WITH THE CUSTOMER.
THIS CUSTOMER FEEDBACK LOOP IS
ESSENTIAL FOR IMPROVING THE QUALITY
OF THE SERVICE.”
–Werner Vogels, Amazon
https://queue.acm.org/detail.cfm?id=1142065

4. @kmugrage
WE KNEW EVERYTHING
▸ Defined Continuous Integration
▸ Created the first (or second) CI server
▸ Created Selenium

5. @kmugrage
JAVA – WRITE ONCE, RUN ANYWHERE
▸ Developed a system on Windows laptops to be deployed to a Solaris cluster
▸ Did all of the right Continuous Integration things
▸ One small issue…

7. @kmugrage@kmugrage
HOMEWORK

8. YOU ONLY HAVE TO
CHANGE ONE THING
TO DO THE DEVOPS

9. YOU ONLY HAVE TO
CHANGE ONE THING
TO DO THE DEVOPS
EVERYTHING

10. @kmugrage
THE CHANGES
▸ (Re)define words for your organization
▸ Change your organization to enable DevOps
▸ Use modern architectures and technologies
▸ Use Continuous Delivery to safely deploy on demand

11. FOR YOUR
ORGANIZATION
REDEFINE WORDS

12. @kmugrage
WHAT ISN’T DEVOPS
▸ A Toolset
▸ A Role
▸ A Team

13. @kmugrage@kmugrage
IT’S VERBS, NOT NOUNS
developING and operatING

14. @kmugrage
CAMS
▸ Culture
▸ Automation
▸ Measurement
▸ Sharing
https://blog.chef.io/2010/07/16/what-devops-means-to-me/

15. @kmugrage
CALMS
▸ Culture
▸ Automation
▸ Lean
▸ Measurement
▸ Sharing
https://blog.chef.io/2010/07/16/what-devops-means-to-me/

16. @kmugrage@kmugrage
“DEVOPS: A CULTURE WHERE PEOPLE,
REGARDLESS OF TITLE OR BACKGROUND,
WORK TOGETHER TO IMAGINE, DEVELOP,
DEPLOY AND OPERATE A SYSTEM.”
–Me
https://kenmugrage.com/2017/05/05/my-new-definition-of-devops/

17. TO ENABLE
DEVOPS
CHANGE YOUR ORG

18. @kmugrage@kmugrage
TRADITIONAL MODEL
Development Teams Testing Team Operations Team

19. @kmugrage@kmugrage
“ANY ORGANIZATION THAT DESIGNS A
SYSTEM (DEFINED BROADLY) WILL PRODUCE
A DESIGN WHOSE STRUCTURE IS A COPY OF
THE ORGANIZATION'S COMMUNICATION
STRUCTURE.”
–Mel Conway
http://www.melconway.com/Home/Conways_Law.html

20. @kmugrage@kmugrage
TRADITIONAL MODEL
Development Teams QA Team Operations Team

21. @kmugrage@kmugrage
RENAMING OPS WON’T SOLVE THE ISSUE
Development Teams QA Team DevOps Team

22. @kmugrage@kmugrage
CREATING ANOTHER SILO DOESN’T SOLVE SILOS
Development Teams QA Team Operations Team
DevOps Team

23. @kmugrage@kmugrage
PRODUCT TEAMS

24. ARCHITECTURES
AND
TECHNOLOGIES
USE MODERN

25. @kmugrage@kmugrage
THERE'S A PHRASE THAT DEFINES
LEGACY SOFTWARE. "THE STUFF
THAT RUNS OUR BUSINESS"
Me, and a lot of other people

26. @kmugrage
MONOLITHS CAN BE HARD
▸ All functionality is in one process
▸ Scale by replicating the monolith on multiple servers
https://www.thoughtworks.com/insights/blog/microservices-nutshell

27. @kmugrage
DEVELOP SMALLER PIECES
MICROSERVICE ARCHITECTURE
▸ Each element of functionality is in a separate service
▸ Scale by distributing these services across servers,
replicating as needed
https://www.thoughtworks.com/insights/blog/microservices-nutshell

28. @kmugrage
DEFINITIONS MATTER
▸ Need to deploy specific versions at the same time? Not a microservice.
▸ Have a shared data source? Not a microservice.

29. @kmugrage
DON’T REBUILD THE WHOLE THING!
▸ Build services only when you understand the boundaries
▸ Build services where you need to react faster
▸ Build services where you need scalability

30. @kmugrage@kmugrage
DON’T REBUILD THE WHOLE THING!

31. @kmugrage@kmugrage
PRODUCT TEAMS
Car Rental
Consumer
Tax
Hotels
Business to Business
Airlines
Payments

32. @kmugrage@kmugrage
FINANCIAL SERVICES PLATFORM
Edge Load Balancer
Service
Repository
Apply Domain
Event Store
Command Handlers
Event Handlers
Service
Repository
Account Domain
Event Store
Command Handlers
Event Handlers
Service
Repository
Product Domain
Event Store
Command Handlers
Event Handlers
Service
Repository
Customer Domain
Event Store
Command Handlers
Event Handlers
E
V
E
N
T
B
U
S

33. @kmugrage@kmugrage
WITHOUT EVENTS
User Service
Quote Service
Quote Service
Quote Service
Quote Service

34. @kmugrage@kmugrage
EVENT NOTIFICATION
User Service
Quote Service Service Service Service

35. @kmugrage
EVENT SOURCING
▸ You don’t write to the data store, you create an event which writes to the store
▸ The test: You could completely blow away the store and recreate it from the event
stream
▸ You use this model every day (I hope)

36. @kmugrage@kmugrage
HOMEWORK
http://samnewman.io/books/building_microservices/
http://nealford.com/books/

37. WE STILL HAVE TO DEPLOY
SOMEWHERE

38. @kmugrage
AN EXAMPLE OF PLATFORM AS A SERVICE
CLOUD.GOV
▸ Official service of the US Government
▸ 325 required security controls
▸ 269 handled by cloud.gov
▸ 41 shared
▸ 15 handled by customer
https://cloud.gov/overview/technology/responsibilities/

39. @kmugrage@kmugrage
THE CLOUD IS JUST
SOMEBODY ELSE’S
COMPUTER
Someone at every conference

40. @kmugrage@kmugrage
PRODUCT TEAMS

41. @kmugrage@kmugrage
PRODUCT TEAMS
Platform Team Compliance Team Security Team

42. TO SAFELY
DEPLOY MORE
OFTEN
USE CONTINUOUS DELIVERY
https://commons.wikimedia.org/wiki/File:Continous_Delivery_by_Jez_Humble
_and_David_Farley.jpg

43. CONTINUOUS
INTEGRATION
A PREREQUISITE TO CD

44. @kmugrage@kmugrage
CI THEATRE
https://www.gocd.org/2017/05/16/its-not-CI-its-CI-theatre/
The ThoughtWorks tech radar recently
recommended putting a hold on the tech team
anti-pattern, CI Theatre. CI Theatre describes
the illusion of practicing continuous integration
(CI) while not really practicing it.

45. @kmugrage@kmugrage
CI THEATRE
In another ThoughtWorks study only 10%
of participants acknowledged that having
a CI server was not the same as practicing
CI.
https://www.gocd.org/2017/05/16/its-not-CI-its-CI-theatre/

46. @kmugrage@kmugrage
ARE YOU PRACTICING CI?

48. CONTINUOUS
DELIVERY

49. @kmugrage@kmugrage
CONTINUOUS DELIVERY IS THE ABILITY TO GET
CHANGES OF ALL TYPES—INCLUDING NEW FEATURES,
CONFIGURATION CHANGES, BUG FIXES AND
EXPERIMENTS—INTO PRODUCTION, OR INTO THE
HANDS OF USERS, SAFELY AND QUICKLY IN
A SUSTAINABLE WAY.
Jez Humble
https://continuousdelivery.com/

50. @kmugrage@kmugrage
CONTINUOUS DELIVERY IS
WHAT YOU “DO” AS PART OF
A DEVOPS CULTURE
Me

51. @kmugrage@kmugrage
CONTINUOUS DELIVERY PIPELINE

52. @kmugrage@kmugrage
CONTINUOUS DELIVERY VS CONTINUOUS DEPLOYMENT
http://gofor.cd/cd_vs_cd

53. @kmugrage@kmugrage
CONTINUOUS DELIVERY VS CONTINUOUS DEPLOYMENT
http://gofor.cd/cd_vs_cd

54. @kmugrage@kmugrage
OUR TEAMS
Product Team Security Team Compliance Team

55. @kmugrage@kmugrage
OUR CONTINUOUS DELIVERY PIPELINE
UNIT
TESTS
FUNCTIONAL
TESTS
DEPLOY
STAGING
DEPLOY
PRODUCTION

56. @kmugrage@kmugrage
CONTINUOUS DELIVERY IS NOT
JUST CONTINUOUS INTEGRATION
WITH A PLUGIN AND A COUPLE
EXTRA STEPS
Me

57. @kmugrage
EXAMPLES OF THINGS WHICH ARE BAD
▸ Deploying insecure software
▸ Deploying non-performant software
▸ Deploying non-complying software
▸ Deploying ineffective software

58. @kmugrage@kmugrage
THE PURPOSE OF A CONTINUOUS
DELIVERY PIPELINE IS TO KILL A
RELEASE CANDIDATE
Me, and a lot of other people

59. @kmugrage@kmugrage
OUR CONTINUOUS DELIVERY PIPELINE
UNIT
TESTS
FUNCTIONAL
TESTS
DEPLOY
STAGING
DEPLOY
PRODUCTION
SECURITY TESTS (OWASP, OTHERS)
COMPLIANCE TESTS (SERVERSPEC,
INSPEC)

61. SORRY, THERE’S NO SILVER BULLET
BUT THESE ARE SOLVED PROBLEMS
AND THERE IS A LOT OF HELP

62. @kmugrage
SUMMARY
▸ Redefine words for your organization
▸ Change your organization to enable DevOps
▸ Use modern architectures and technologies
▸ Use Continuous Delivery to safely deploy more often

63. @kmugrage
@goforcd
https://www.gocd.org/