Lessons from Production Incidents at Monzo Bank - Oliver Beattie (Monzo) @ContainerCamp
Lessons from Production Incidents at Monzo Bank - Oliver Beattie (Monzo)  @ContainerCamp
Uploaded April 2020 | Updated November 2026, 18 hours ago
Monzo is as much a technology company as it is a bank. As well as the extreme resilience and security requirements that come with handling peoples’ money, being a startup necessarily means Monzo must be able to move fast. The platform that meets this challenge comprises hundreds of micro-services running as thousands of containers under Kubernetes, communicating using a service mesh. Operating and scaling this infrastructure for nearly 2 years has taught us many important lessons the hard way. This talk will dive into several production incidents that Monzo has experienced, their causes and effects, and the architectural and operational lessons we learned from them.
Lessons from Production Incidents at Monzo Bank - Oliver Beattie (Monzo)Continuously delivering apps to Kubernetes using Helm - Adnan Abdulhussein (Bitnami)Scott Johnston: Whats new in the world of Docker and Docker Hub?Kubernetes: Changing the way that we think and talk about computing - Mandy WaiteEverything we need to know about devops we learned from sci-fi movies - Casey BissonLessons from running potentially malicious code inside containers - Ben HallDistributed Command Execution using Containers and Cog -  Vincent De Smet (honestbee)Jérôme Petazzoni: Docker in productionWilly Wonka of Containers - Jessie FrazelleTuning docker network for large scale production workload - Sunil Ganatra (IBM)Introducing a Kubernetes Operator for Azure Databricks - Azadeh Khojandi (Microsoft)Running Hadoop Clusters as a Service in Production using Containers - Rachit Arora (IBM)
Container Camp |

Lessons from Production Incidents at Monzo Bank - Oliver Beattie (Monzo)

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER