Please log in to watch this conference skillscast.
What happens when your platform reaches a point where you need to rethink previous decisions? How does the microservice architecture hold up against changes spanning across large parts of the system? Monzo has several payment processors used by hundreds of thousands of people daily and handling millions of pounds. Irina will share with you how Monzo used stateless services to re-build one of them to be robust and extendable. And how they replaced it live without anyone noticing.
YOU MAY ALSO LIKE:
- How We Use Go to Build a Distributed Bank (SkillsCast recorded in November 2017)
- Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 18th - 19th February 2021)
- Android Architecture with Jorge Ortiz-Fuentes (Online Course on 22nd - 24th February 2021)
- Accelerated Software eXchange Forum (Online Conference on 18th February 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- Evolutionary Architecture (SkillsCast recorded in January 2021)
- What an Architect Can Learn from Retrospective Failures (SkillsCast recorded in December 2020)
How Monzo Replaced a Critical Live System Without Anyone Noticing
Irina is a backend engineer at Monzo. She has been writing Ruby since Rails 2.1 and had seen every possible design pattern implemented, used and abused in a range of Ruby apps varying from broadcasting platforms to accounting software. Now she's out of the Ruby world and helping to build a bank with Go microservices.