4. Disclaimer #1
The opinions expressed in this presentation and on the following
slides are solely those of the presenters and not necessarily
those of Scania as a whole.
5. Disclaimer #2
Tools are only randomly selected. Scania does not value these
more than those not mentioned…
…except for Perforce
6. Scania as an IT company
• ~1200 workers (800+400) @ Scania IT
• ~1400 apps (mix of build and bought)
• ~2500 servers (win, Linux, MF, iSeries)
• ~1400 TB data
• Main site -> Södertälje, Sweden
• Regional site -> Sao Paolo, Brazil
• Supports Scania Globally
• Application, infrastructure, EUS
7. Perforce @ Scania
• Perforce customer since 2007
• Disk usage on servers 1.8 TB
• 1000+ users
• 1000+ change lists submitted per day
14. Automation – Deployment Pipeline
Version Control
Pull & Push several
times a day
Continuous
Integration Server
- Build
- Test
- Package
Target Servers
(Dev, Staging, Prod)
Deploy Server
Version Everything
- Code
- Tests
- Configuration
- Database
- Infrastructure
18. Level 1
Level 2+3
Infrastructure As A Service
Infra/
Operations
Feature
Team
Feature
Team
Feature
Team
Feature
Team
GUI
Business
Logic
Database
Virtual Machine ESB Network Change Management Database Monitoring
Forward
19. Infrastructure As A Service
Infra/
Operations
Feature
Team
Feature
Team
Feature
Team
Feature
Team
GUI
Business
Logic
Database
Virtual Machine Web server Load Balancer Change Management Monitoring
You build it You
run it!
Infrastructure
as code
Cultural Technical
21. HW / Virtualization
Storage
Network
Data center
Application Server / Web Server
Database
OS
Services
Services
Services
Services
Services
Services
Services
.NET Java Oracle
26. 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
Microservices
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
28. Learnings: Dev-to-Dev
• Find end user feedback and try to act on it
• Learn to work on Trunk
• Do not rely on database backup for dev/test
• Never blame bad code
• Ops guys are not pure evil persons
• Avoid “Hero-Based Culture”
Water – Defines the upfront project planning process that typically happens between IT and the business.
Scrum – An iterative and adaptive approach to achieving the overall plan that was first laid out in the 'Water' stage.
Fall – A controlled, infrequent production release cycle that is governed by organizational policy and infrastructure limitations.
(From: http://www.infoq.com/news/2011/12/water-scrum-fall-is-the-norm)
You have still automation to do if…
You can’t have a dev environment up and running with one single command
Someone does manual regressions
Prepare test data on test environment
You have to order a server
Anyone have to log in to a server
Someone does manual installations
Funktionella silos – suboptimeringar
Många överlämningar (exempel HS)
Långt från kunden
Inga tjänster som kunden vill ha
Friktion mellan grupperingar
Vi har nya roller efter “kund”
Virtuellt organiserade efter leverans
Kommer närmare kund
Utvecklar tjänster som kunden vill ha
”It’s a trade from code complexity to operational complexity”
Martin Fowler:
https://www.youtube.com/watch?v=wgdBVIX9ifA
http://martinfowler.com/articles/microservices.html
Adrian Cockcroft:
https://www.youtube.com/watch?v=nMTaS07i3jk&feature=youtu.be
Gene Keen, Randy Shoup
http://youtu.be/MRa21icSIQk 43:00
Randy Shoup:
http://gotocon.com/dl/goto-cph-sept-2014/slides/DeanWampler_and_EvaAndreasson_and_KevlinHenney_and_RandyShoup_WheresCaptainKirkChartingACourseThroughEnterpriseArchitecturePartI.pdf