Cloud & DevOps World

Slide deck used at Cloud & DevOps World in June, 2016 by Tim Savage https://tmt.knect365.com/cloud-devops-world/speakers/tim-savage

Transcript

1. Can you trust Cloud Foundry to save a life? (to save 10,000?)
2. Armakuni • Cloud native transformations • Engineering for the cloud • Application development in the cloud Introductions Tim Savage, Armakuni Tim Savage • Director • Full stack engineer • Product owner @armakunihq http://www.armakuni.com
3. ▪ Well known UK Charity ▪ Vision: “Just world free from poverty” ▪ £1 billion since its inception in 1985 ▪ Campaigns: Red Nose Day & Sport Relief ▪ 8-12 week campaigns culminating in a telethon event. Introductions Comic Relief
6. 100,000 concurrent web donors
7. 14,000 call centre operators start taking calls
8. Responsibility Armakuni built and run the platform that has to be able to handle all the credit card transactions generated at this point.
9. Its Peaky Traffic...
10. To Summarise the Challenge... 400 donations per second
11. To Summarise the Challenge... ▪ 400 donations per second Web and Call Centre interfaces
12. To Summarise the Challenge... ▪ 400 donations per second ▪ Public and Call Centre interfaces just 7 hours per year
13. To Summarise the Challenge... ▪ 400 donations per second ▪ Public and Call Centre interfaces ▪ 7 hours per year Guarantee £Xty million in donations
14. To Summarise the Challenge... ▪ 400 donations per second ▪ Public and Call Centre interfaces ▪ 7 hours per year ▪ Guarantee £Xty million in donations No second chance
15. To Summarise the Challenge... ▪ 400 donations per second ▪ Public and Call Centre interfaces ▪ 7 hours per year ▪ Guarantee £Xty million in donations ▪ No second chance On a charity budget
16. To Summarise the Challenge... ▪ 400 donations per second ▪ Public and Call Centre interfaces ▪ 7 hours per year ▪ Guarantee £Xty million in donations ▪ No second chance ▪ On a charity budget No practising
17. 400 Real-time card transactions per second 100,000 + 10,000 Concurrent public users + Call centre users 800,000 Donations in a 7 hour window
18. Before 2012? ▪ Java Monolith : : Code to manage, difficult development process ▪ No automated testing : : Manual testing leads to gaps ▪ Manual deployment : : Inconsistencies, time consuming, unrepeatable ▪ Single points of failure : : Infrastructure provider, platform, bandwidth ▪ Multiple partners : : Complex matrix of partners, up to 50 people involved ▪ 1 year feedback cycle : : Changes were only really tested once a year
19. And now?
20. Java Monolith >> Microservices Architecture
21. ▪ TDD/BDD ▪ Unit ▪ Integration ▪ Security ▪ Load ▪ ... all automated ▪ ... ... all run every time a commit is made No Automated Testing >> Full Suite of automated tests
22. Manual Deployment >> Continuous Deployment ▪ Continuous deployment is utterly dependant on automated testing ▪ Now, all code changes deploy to production on success ▪ (We use Concourse CI)
23. Single Points of Failure >> Commoditised Services ▪ Where we have an external dependancy we have “commoditised” it ▪ Multiple payment service providers ▪ Multiple infrastructure providers ▪ If it doesn’t have an api, we aren’t interested!
24. Multiple Partners >> Single Partner ▪ We have reduced Comic Reliefs dependancy from multiple partners and 40-50 people down to a team of 4 ▪ Everything is code - nothing is done manually, so all knowledge is stored as code +
25. 1 year feedback cycle >> 15 minute feedback cycle ▪ Every code change pushed goes through our entire suite of tests before making its way to production ▪ Developers can make changes with confidence
26. What?
27. • PaaS - Platform as a Service • Lots “out of the box”: ◦ Health monitoring ◦ Routing ◦ Centralised logging ◦ Easy service integration (eg data sources) • Separates applications from infrastructure • Standardised contract for developers
28. Architecture Front End Shard DNS FRONT-END US EAST 1 Cloud Foundry (BOSH/EC2)
29. Architecture Add some apps DNS FRONT-END US EAST 1 Cloud Foundry (BOSH/EC2) 28 microservices
30. Architecture Now add some continents and IaaS providers DNS FRONT-END US EAST 1 Cloud Foundry BOSH/EC2 FRONT-END EU WEST 1 Cloud Foundry BOSH/EC2 FRONT-END LONDON Cloud Foundry BOSH/VMWARE
31. Architecture Add Management layer DNS FRONT-END US EAST 1 Cloud Foundry BOSH/EC2 FRONT-END EU WEST 1 Cloud Foundry BOSH/EC2 FRONT-END LONDON Cloud Foundry BOSH/VMWAR E REPORTING EU CENTRAL Cloud Foundry BOSH/EC2 LOGS
32. Architecture Now deploy it all
33. To Conclude ▪ SUCCESSFUL : : Last 4 campaigns, £Millions processed ▪ MANAGEABLE : : 1 team to manage ▪ TEAM : : 50 to 4 ▪ COST : : £Millions (commercially comparable) to < £300k ▪ AGILE : : Even now, the team can be very agile
34. Can you trust Cloud Foundry to save a life? To save 10,000?
35. ▪ @armakunihq ▪ armakuni.com ▪ tim.savage@armakuni.com