The presentation slides of the state of the DevOps journey at Scania Connected Services. The presentation was held in Berlin on April 24, 2017.

1. Berlin, April 24th 2017
Anders Lundsgård
The DevOps journey in an Enterprise
- From monthly release cycles to minutes
DevOps

2. Agenda
 DevOps transformation at Scania
 Continuous Integration / Continuous Delivery
 Microservices architecture
 Cloud adoption
2

3. ~250.000 connected vehicles
~100 engineers
~15 years of age
Scania Connected Services

4. Disclaimer
The opinions expressed in this presentation
and on the following slides are solely those of
the presenter and not necessarily those of
Scania as a whole.

5. Our software evolution
‘90s
Spaghetti Code
‘00s
Growing monoliths
‘10s
Microservices era

6. The reality today

7. We at infra need to be an enabler for
developers. Enable automatic deployments
and roll-backs.
Creating tools/dashboards with relevant
KPI’s so that the developer can fast and
easily see the consequences of a deployment.
- Mattias Järnhäll, Infrastructure manager
2014.03.03 on Scania social network

8. in the early days…
DevOps movement
More features
quicker Stability

9. Smaller increments
enables stability

10. Shared understanding and common goals

11. The foundation: Continuous Integration
Version everything Automation
Claim over Blame
Trunk based
development

12. CODE
IN PROD
PENDING
CODE
NEW
FEATURES
High focus on Limit Work In Progress
= INVENTORY

13. Version Control
Pull & Push several
times a day
Continuous
Integration
Server Target Servers
(Dev, Staging, Prod)
Version Everything
- Code
- Tests
- Configuration
- Database
- Infrastructure
10 minutes
Continuous Delivery is mandatory
Continuous Deployment is optional
Deploy
Server

14. Sounds weird?

15. Sounds weird?Reveal a Secret

16. Reveal a Secret

17. Developers care about
QA and Stability
if…
they get accountable

18. GUI
Database
Infra
Business
Logic
Networking Storage
OS
Integration
Service
1
Service
2 Service
5
Service
7
Service
8
Service
10
Service
12
Service
14
Service
3
Service
4
Service
6
Service
9
Service
11
Service
15
Middleware
Service
13
User Interface
Security Monitoring
Even with Continuous Integration,
fast delivery is hard with 50+
engineers and a large codebase.
Monolith

19. All Infra
needs
User Interface
Service
1
Service
2 Service
5
Service
7
Service
8
Service
10
Service
12
Service
14
Service
3
Service
4
Service
6
Service
9
Service
11
Service
15
Service
13
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
All Infra
needs
GUI
Database
Infra
Business
Logic
Why Microservices?
1. Autonomous teams
2. Build, Test, Deploy SPEED
Microservices

20. Deploy frequency
• Pre 2016
– Agile teams
•Continuous Integration
•12 deploys per year
• 2016
– Autonomous Teams
•Continuous Delivery
•30+ deploys per day
• Pre 2012
– Software projects
•2-3 in parallel
•3 deploys per year
Biggest enablers
1. Microservice architecture
2. Trust and courage from
management

21. Deploy != Release
Business
decision
Feature Team
concern
Feature Team
concern

22. Feature Toggle

23. Tilda 4 makes release to UK market

24. Zero Downtime

25. Visibility

26. 10.000+ unique portal users per month

30. DevOps and Cloud

31. Application
Development
Delivery
Engineering
Infrastructure
Provisioning
Feature TeamsDeveloper Teams
Delivery Engineering
DevOps
Corporate IT
Corporate IT
Connected Services
Shared responsibility
Traditional silos

32. Application
Development
Delivery
Engineering
Infrastructure
Provisioning
Feature Teams
Delivery Engineering
Corporate IT
Connected Services
Shared responsibility
Manage their own
CI pipeline
Infrastructure as Code
for their
Microservices
AWS accounting
IP-plan
Corporate Security
Cloud education
Common tooling
Common infra templates

33. Cloud movement

34. Infrastructure as a Ticket

35. Infrastructure as Code

36. 36
200
301
401
404
500

37. 37
200
301
401
404
500

38. Thank You!
Anders Lundsgård
@anderslundsgard