Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
Our Journey to Containerised Microservices @nickywrightson nicky.wrightson@ft.com By Nicky Wrightson
Slide 2
Slide 2 text
@nickywrightson Nicky Wrightson Principal Engineer & Tech Lead @ FT
Slide 3
Slide 3 text
https://www.ft.com The news business has changed a lot in the last 130 years
Slide 4
Slide 4 text
How can we do more for less money?
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
No content
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
https://www.flickr.com/photos/bluesquarething/5165177846 Containers can fix this
Slide 11
Slide 11 text
Over 200 services … In two regions … All containerised …
Slide 12
Slide 12 text
2. A meandering journey 3. Benefits to us now? 1. Why we chose containers 4. What’s next?
Slide 13
Slide 13 text
1. Why we chose containers
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
https://six-degrees.ft.com/
Slide 16
Slide 16 text
What is a news website without content?
Slide 17
Slide 17 text
5+ weeks dev cycle
Slide 18
Slide 18 text
https://twitter.com/architectclippy/status/570025079825764352?s=09
Slide 19
Slide 19 text
Over 200 services … In two regions … ~550 VMs
Slide 20
Slide 20 text
3 years ago we started to architect for containers
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
We could reduce costs by ~ 80% using containers
Slide 23
Slide 23 text
What about serverless?
Slide 24
Slide 24 text
2. A meandering journey 1. Why we chose containers
Slide 25
Slide 25 text
Content in Containers == CoCo
Slide 26
Slide 26 text
Containerise every service
Slide 27
Slide 27 text
Monitoring
Slide 28
Slide 28 text
Change database and programming language at the same time!!
Slide 29
Slide 29 text
It was not all plain sailing
Slide 30
Slide 30 text
Stateful services do not play nice
Slide 31
Slide 31 text
“We need a bigger boat” Richard Dreyfus in Jaws (1975) Image: http://goo.gl/4r26gS
Slide 32
Slide 32 text
We kept losing our live clusters
Slide 33
Slide 33 text
No content
Slide 34
Slide 34 text
No content
Slide 35
Slide 35 text
Monitor and react at the right levels
Slide 36
Slide 36 text
No content
Slide 37
Slide 37 text
React quickly to security patching
Slide 38
Slide 38 text
Deployment needs to be automated, consistent, repeatable and have the ability to be rolled back
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
Massive shift in operational thinking
Slide 41
Slide 41 text
If it is hard do it more often If it is really hard automate it!
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
How to iterate on 200 services at the same time?
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
“Stateful services are painful to containerise” Nicky Wrightson January 2016
Slide 48
Slide 48 text
2. A meandering journey 1. Why we chose containers 3. Benefits to us now?
Slide 49
Slide 49 text
Containers in general can benefit EVERYONE
Slide 50
Slide 50 text
No content
Slide 51
Slide 51 text
Operationally supportable
Slide 52
Slide 52 text
Kubernetes will fix that ….
Slide 53
Slide 53 text
Deployments are more graceful
Slide 54
Slide 54 text
2. A meandering journey 1. Why we chose containers 3. Benefits to us now? 4. What’s next?
Slide 55
Slide 55 text
Enhance our initial approach
Slide 56
Slide 56 text
Get someone else to do the heavy lifting
Slide 57
Slide 57 text
One cluster to rule them all …
Slide 58
Slide 58 text
Federation
Slide 59
Slide 59 text
In Conclusion
Slide 60
Slide 60 text
No content
Slide 61
Slide 61 text
@nickywrightson nicky.wrightson@ft.com Thanks