Continuously Delivering Microservices to the Cloud: A Case Study - DevOps & Microservices Summit 2017

These days if you're not doing a "digital transformation", you're not one of the cool kids. Going to the cloud, adopting microservices and transitioning to DevOps sound like a lot of fun, but more often than not things don't go as smoothly as expected. At an international transport company, we've put theory to practice.

In this talk we'll shed a light on what we've experienced, where we've succeeded, and some vital lessons we've learned. Get an idea of our tech stack, consisting of Spring Cloud, Google Cloud Platform, Jenkins, Spinnaker and Prometheus and more. Join us to get some tips and tricks and what to look out for when continuously delivering microservices to the cloud.

Transcript

1. Continuously Delivering Microservices to the Cloud A Case Study
4. Provisioning new instances for scaling takes ages. Heavy load in one component requires everything to scale up.
5. Change one thing, Change everything. Such minor changes, Such huge consequences.
6. High-performing IT organizations deploy 200x more frequently with 2555x shorter lead times they have 3x fewer failures and recover 24x faster - Puppet labs state of devops report 2016
9. F A S T A D A P T E R S
12. DEVOPS
13. Gentlemen you can't fight in here, this is the War Room! - President Merkin Muffley
14. YOU BUILD IT, YOU RUN IT. - Amazon CTO Werner Vogels
15. Anyone who doesn’t do this will be fired. Thank you; have a nice day! - Amazon CEO Jeff Bezos
18. Microservice Architecture Monolithic Architecture
22. 0 2 10 60 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 M ON T HS
34. Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations. - Conway’s Law
42. Thank you for listening @ t y s e w y n @ andr e as e v e r s T im . Ys e w y n@ or dina. be Andr e as . E v e r s @ or dina. be or dina. be or dina-j w or k s . git hub. io