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.

Ian Margetts - ASOS’ Journey to Continuous Deployment

699 views

Published on

ASOS has been improving its world for the last 8 years. It has grown from 2 teams in 2008 to over 50 in 2017, increased revenues massively in the same period and then embarked on a major re-architecture of its codebase with a large emphasis on cloud. This talk is about how we have approached the evolution of DevOps during that period – some of the mistakes we have identified and how it’s so not about tools but people, getting good people to care about Platform Engineering and engendering that behaviour in to teams.

Published in: Technology
  • Be the first to comment

Ian Margetts - ASOS’ Journey to Continuous Deployment

  1. 1. JOURNEY TO CONTINUOUS DEPLOYMENT IAN MAR GETTS
  2. 2. 2016 confidential AGENDA. • Who are we? • The Background • Why Re-architect? • V1 of DevOps • Alignment to Re-Platforming • The Results • What’s Next 2016 confidential
  3. 3. 2016 confidential T H E N U M B E R 1 F A S H I O N D E S T I N AT I O N F O R T W E N T Y S O M E T H I N G S W E S E L L O V E R 8 5 , 0 0 0 P R O D U C T S 1 3 9 M S I T E V I S I T S I N D E C E M B E R 2 0 1 6 1 4 M A C T I V E C U S T O M E R S F R O M A R O U N D T H E W O R L D W E S E L L T O A L M O S T E V E R Y C O U N T R Y I N T H E W O R L D S T I L L G R O W I N G O V E R 2 5 % Y O Y
  4. 4. 2016 confidential2016 confidential DIGITAL PLATFORM PRODUCT & CONTENT CUSTOMER ENGAGEMENT 3rd Party Solutions E.g Fred Hopper 3rd Party Solutions E.g Fred Hopper CORE eCOMMERCE Bag Service Bag Service Checkout Service Checkout Service Payment Service Payment Service Search Service Search Service Customer Profile Service Customer Profile Service Loyalty Service Loyalty Service STOCK & FULFILMENT StockStock Delivery OptionsDelivery Options ASOS CHANNELSASOS CHANNELS Product Service Product Service INTEGRATION PLATFORM ENTERPRISE PLATFORM Supply ChainSupply Chain FinanceFinance DATA PLATFORM Data Services PeoplePeople Data Lake StockStock RetailRetail OrderOrder ProductProduct IdentityIdentity PropensityPropensity
  5. 5. 2016 confidential2016 confidential DOMAIN ... Development Teams (1 or more) Platform Team Head Of Technology For Domain Principal Architect Principal Engineer Lead Business Analyst Lead QA Service Delivery Programme / Project Manager Shared Across Domain Supporting Domain Resources Solution Architect (1 or more) Platform Team Platform Team Platform Team Platform Lead Product Manager UX Designer (Team Dependent) Technology Core Functions PMO SecurityEnterprise Architect Change Mngmt Etc. Senior Business Analyst Business Analyst Agile Delivery Manager Dev Team Software Engineers QA (1 or more) Data Engineer (Team dependent)
  6. 6. 2016 confidential THE BACKGROUND 17.8 37.7 71.7 149.3 205 324 482 754 955 1119 1444 0 200 400 600 800 1000 1200 1400 1600 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 Revenue (£m) Total 2 0 0 8 • £72m Revenue • 2 x software engineering teams • Single, monolithic code base hosted in traditional datacentre • Semi-automatic deployment process 2 0 1 6 • £1.5b Revenue • 54 x software engineering teams • Codebase largely re-architected and hosted in Azure • Fully automated deployment process
  7. 7. 2016 confidential2016 confidential • Technology constraints • Monolithic Application • Slow to change – Test and Deploy • Presentation & Logic intertwined • Unstable • 3rd Party Proxies hacked in • No resiliency • Business constraints • Single language • Single currency • Single channel (Web) Why re-architect? Content Delivery Network (Globally Deployed) Upto7seconds
  8. 8. V1 of DevOps A Centralised Framework • Used by everyone to push code from test to production • Build once, deploy many • Shared ownership (anyone can develop) • Custom to the needs of ASOS Centralised ALM / DevOps • ‘Own’ deployments and path to live to ensure consistency • Make core changes to framework • Support teams on making extensions • ‘Own’ environment management to ensure consistency
  9. 9. 2016 confidential THE RESULTS… R ELEA SES IN C R EA SED EXPONENTIALLY IN 4 YEARS, ATTR IB U TA B LE TO: • ALM framework development • Improved environments • Release management improvements • Start of the re-architecture into Azure 20 40 141 272 332 0 50 100 150 200 250 300 350 2011 2012 2013 2014 2015 Releases 2016 confidential
  10. 10. Aligning DevOps to Re-Platforming Re-architecture of the code base • From one code base to hundreds • Truly decoupled micro-services architecture • Move to Azure Emergence of the Platform Teams • From project to platform based • More responsibility for code and infrastructure • Both development and support responsibilities Release Demand • Business hunger for more regular features
  11. 11. What did we do? Goals • Empower teams • Improve team competency • Devolve team support • Support cloud How • Tooling • Rollout of competency model • Platform engineering – central and devolved
  12. 12. Did it work? • Teams taking ownership • Reduction in release effort • Resolving challenges more quickly (and earlier) • Metrics based conversations • All components released prior to Black Friday Challenges • Shifting Accountability to Platforms • Doing it at Scale • Business Demands
  13. 13. 20 40 141 272 332 487 1305 0 200 400 600 800 1000 1200 1400 2011 2012 2013 2014 2015 2016 2017 Releases
  14. 14. 2016 confidential WHAT’S NEXT? CULTURE • Get to grips with Autonomy • Drive Platform Engineering to Teams • Metrics based conversations to drive Continuous Improvement • DevOps to Ops TECHNOLOGY • Automate (where appropriate) • Data, data, data • Operate at scale • Information 2016 confidential
  15. 15. 2016 confidential2016 confidential QUESTIONS?

×