This document discusses DevOps concepts including: 1. DevOps is a journey to improve collaboration between development and operations teams, not a process or methodology. It focuses on a continuous transformation through experiences shared. 2. Early DevOps practices include continuous integration to reduce bugs, deploying features faster through automation, and improving quality. 3. As applications grow, teams face challenges like long merge times and deploy delays. Adopting microservices architecture and infrastructure as code helps teams deploy individual services independently and quickly. 4. Organizing teams around business capabilities and services using a Lean Startup approach allows independent deployments and faster feedback. Monitoring everything is also important for DevOps.

1. Christophe Marchal | Software Architect
DevOps e a nova Cultura

2. christophe.marchal@ilegra.com
@toff63
http://github.com/toff63
http://francesbagual.net
About me

3. www.ilegra.com

4. What DevOps is not
❏ Process
❏ Methodology
❏ Set of Practices
❏ Set of Tools
❏ Certification
❏ Team / Role / Department
❏ SaaS
❏ Framework

5. What DevOps is
❏ A journey to a desirable state
❏ A way of thinking
❏ A continuous transformation process
❏ The result of experiences
❏ A movement ...

6. Start up example
Let’s
deploy!

7. Start up example
Open a
ticket

8. Start up example

9. Start of the success

10. Application grow
Let’s
deploy!

11. Application grow
Too
unstable!

12. Start some XP Practices
Only commit in trunk
Use of SCM tool
Continuous
Integration
➔ unit tests #compilation
➔ integration tests #runtime
➔ acceptance tests #runtime

13. Continuous Integration
Compilation
Unit Tests
Deploy em
Staging
Integration
Tests
Automatic
Acceptance
Tests
User
Acceptance
Tests

14. Quality Improvement

15. Team and Application keep growing
❏ Time spent merging
❏ Time spent compiling
❏ Time spent testing
❏ Time to put a feature in production
❏ Application Response time
❏ Hardware consumption

16. Isolation via Modularization

17. Move dependency from Compilation
to Runtime

18. New Deploy
Service
Service

19. Application grow
I cannot
deploy
separately!
This is safe!
Only 1 line of
code changed
Service Service
Service Service

20. Service dependencies
Service
Service
Service
Service
Service

21. SOA

22. SOA
Service Service
Contract
Service
➔ Dependency only depends on service contract
➔ Service contract has versions
➔ No branch
Service
Contract
Contract
Service
Contract
Contract
➔ unit tests #compilation
➔ contract tests #compilation
➔ integration tests #runtime
➔ acceptance tests #runtime
➔ performance tests #runtime

23. Update one service
I only
deploy 1
service
This is safe!
Only 1 line of
code changed
Service
Contract

24. Conway’s Law
“Organizations which design systems … are
constrained to produce designs which are
copies of this communication
structures of these organizations”
Melvin Conway, 1968

25. Organize teams around services
User
User
User
BA
BA
BA

26. Every team working as a Lean Startup

27. Number of tickets
Need to
automatize
➔ unit tests #compilation
➔ contract tests #compilation
➔ integration tests #runtime
➔ acceptance tests #runtime
➔ performance tests #runtime
➔ deploy automation tests #infra
Infrastructure
as a code

28. Continuous Deployment
➔ Availability
➔ Rollback
➔ Data synchronization
➔ Scalability
➔ Cost/Benefit

29. Continuous Delivery
Compilation
Unit Tests
Deploy
Staging
Integration
Tests
Automatic
Acceptance
Tests
User
Acceptance
Tests
Stress Test
Deploy
Production

30. Monitor Everything

31. Feature Toggle

32. Isolation Build once, Deploy everywhere

33. Configuration Management
REST Service
Key Value database
Filesystem
Environment
Variable

34. Green / Blue Deployment

35. Canary Deploy

36. Deploy the same way everywhere

37. Virtualization

38. Provisioning
Operation System
Virtual box images

39. Local Machine
Operational System
Operational System Application
Application
Operational System
Application

40. Still not there
Production Local Machine

41. Still not there
Kernel Linux
Docker Repository

42. Scripting

43. Many, many, many servers
➔ job scheduling
➔ bind containers to physical servers

44. New Operational System

45. Failure Everywhere

46. Test in Production

47. Christophe Marchal | Software Architect
Thanks for your Attention