Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Cloud Journey in an Enterprise - CoDe-Conf - Copenhagen October 11, 2018

189 views

Published on

Public presentation about Scania's Cloud migration. Why Scania goes for public cloud and how we organize and utilize cloud computing. New content is (among other details from latest learnings) an example on serverless code hosted on AWS.

  • Be the first to comment

The Cloud Journey in an Enterprise - CoDe-Conf - Copenhagen October 11, 2018

  1. 1. The Cloud Journey in an Enterprise ANDERS LUNDSGARD, SCANIA CONNECTED SERVICES 2018-10-11, Copenhagen
  2. 2. • Why Cloud? • How does Scania Cloud? • Our Rules of Play Agenda
  3. 3. ~350.000 connected vehicles ~150 engineers ~15 years old Scania Connected Services 24/7 /5 (Q3 2017)
  4. 4. ~350.000 connected vehicles ~150 engineers ~15 years old Scania Connected Services 24/7 /5 Anders Lundsgård Senior Engineer, Delivery Engineering @anderslundsgard (Q3 2017)
  5. 5. ~350.000 connected vehicles ~150 engineers ~15 years old Scania Connected Services 24/7 /5 Anders Lundsgård Senior Engineer, Delivery Engineering @anderslundsgard (Q3 2017)
  6. 6. 9 Scania Connected Services Message Platform Remote Diagnostics Fleet Management Tacho Does not scale!
  7. 7. 10 Scania Connected Services
  8. 8. • 3-8 people • Requirements • Technologies • Quality • Deployment • Operations 11 Autonomous Teams that fully own their services
  9. 9. • 3-8 people • Requirements • Technologies • Quality • Deployment • Operations 12 Autonomous Teams that fully own their services
  10. 10. Deploy frequency • 2015 – Agile teams • 12 deploys per year • 2016 – Autonomous Teams • Continuous Delivery • 30+ deploys per day • 2011 – Software projects • 2-3 in parallel • 3 deploys per year 1. Microservice Architecture 2. Trust and courage from management Continuous Integration
  11. 11. Version Control Pull & Push several times a day Continuous Integration Server Target Servers (Dev, Staging, Prod) Version Everything Code Tests Configuration Database Pipeline Infrastructure 10 minutes Deploy Orchestrator Reliable changes must also include Infrastructure TO MASTER!! Infrastructure
  12. 12. Quiz Who is this? 15
  13. 13. Cloud 16
  14. 14. Cloud Adoption 20162014 Cloud First 2019 Cloud Only
  15. 15. Cloud – Return on Investment Resistance Legacy Education Value benefits of cloud
  16. 16. Organize for 1500+ Engineers = Feature TeamFT DE = Delivery Engineering (Supporting) DE FT FT FT FT FT FT FT FT DE FT FT FT FT FT DE FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT FT Multiple other departments co-located in same building Cloud Adoption Lift and shift Greenfield Dev-teams that move to “DevOps”-teams with no investment tend to struggle in their cloud journey
  17. 17. Supporting Cloud engineers What should they NOT DO? 20 Deployments
  18. 18. 1. Enabling feature teams to iterate as fast as possible 2. Cloud on-boarding and education 3. Core infrastructure − Networking, IAM, DNS, … 4. Automation tooling 5. Security awareness − Automated audits to Security Lead − Security Compliance Validator (cfn_nag) 6. Cost awareness − Billing reports to Cloud Leads 21 Supporting Cloud engineers mission
  19. 19. Key decisions in our AWS setup Version Control cloud enabled AWS multi account strategy Immutable infrastructure In each Feature Team! Read Only in Prod for human beings FREE NO BASTION
  20. 20. 23 Warning – some code will be shown
  21. 21. Example – ScaniaCoin microservice (Code for a backend API used in The Game by Scania) API Gateway Lambda DynamoDB GitLab CI
  22. 22. Code Tests Infrastructure Database Deployment Pipeline
  23. 23. …in the past… Code is the same as in the past Tests are the same as in the past Manual tweaks in Jenkins pipe Ordering of servers No patching of servers Order of DNS aliases Order of backups No licensing of software No downtime on releases No downtime on releases Order of FQDN in Load Balancer Order of alarms No capacity planning No order of service users No secrets!!
  24. 24. No heroes!
  25. 25. 32 Thank You! Anders Lundsgård @anderslundsgard

×