DevOps practices has been evolving and changing so rapidly, but the maturity of the main principles are almost defined decades ago. I will be discussing about the higher level principles of DevOps and how those fit with the current day practices, including the challenges during applying those into your environment

1. DevOps Higher Maturity Levels
Derya Sezen
@derya_sezen

2. Derya SEZEN, 38 ANS, CONSULTANT @ KLOIA.CO.UK
BOTH WORKED AS DEV AND OPS
LINUX USER SINCE 1998
LOVES CYCLING
WRITES ABOUT TECH @ blog.kloia.com
@derya_sezen
deryasezen.com

3. DevOps & Microservices Consultancy
We consult you move towards Containerization, Automated Provisioning, Deployment/Release
Automation, Test Automation, Performance Tuning and moving to Cloud …
10+ Enterprise&Startup AWS Migrations
10+ DevOps Transitions
50+ DevOps&AWS Hands-on Trainings
3 Enterprise Microservices Transitions
1 Enterprise CQRS Transition
(w/ our OSS framework: eventapis.kloia.com)

4. Partnerships

5. DevOps Maturity Meter

7. Trunk-based Development

8. Trunk-based Development
No* branching on version control
All develop on trunk, inc. bug fixes
No Code freeze
No Merge
“Anti gitflow”
* ideally

9. Continuous Deployment

12. Behaviour Driven Development

13. Behaviour Driven Development

14. Behaviour Driven Development
Gherkin

15. Behaviour Driven Development
Gherkin
GIVEN i navigate to www.domain.com
WHEN i click “Sign In”
AND i enter “Username”
AND i hit “FakePassword”
THEN i will receive “Check your username/password and try again”

16. Deploy ≠ Release

17. No rollbacks, always rollforward

18. “Everything-as-code”
● Analysis
● Documentation
○ Swagger
○ Automated
● Infrastructure
○ Router-switch
○ Firewall
○ OS
● Database schema
● Datafeed
● Deployment Pipeline
● ....

19. Pets vs Cattles
● Given names
● Unique
● Care
● When ill, nursed
● Given numbers
● Identical (almost)
● Livestock
● When ill, replaced

20. Pets vs Cattles
● Naming: No instance name (Automated), Service Naming
● Care: No ssh/remote desktop
● ill: Reprovision

21. Immutable deployment
● Not Blue-Green
● Don’t touch to the working environment
● Configuration Drift / History → long uptime is not welcome → Redeploy

22. Autonomic Computing/Infrastructure
IBM, 2002
1. Basic Level
2. Management Level
3. Predictive Level
4. Adaptive Level
5. Fully Automated Level

23. Platform Teams & Business Teams

24. Platform Teams & Business Teams
Classic approach:
● Dev-Test(Developers)
● Staging-Prod(Ops)

25. Platform Teams & Business Teams

26. Business Teams Platform Teams
Focus on software delivery Focus on platform services exploitation
Develop, run and maintain the application using platform services All app environment are production, they have internal Dev-Test
Platform environments
Responsible for production maintenance Responsible for exploitation of the platform services
Business Teams are customers
“Internal Cloud Service Provider” though on-premises or Cloud
Brokerage

27. Derya Sezen
@derya_sezen