# Solving Network Challenges at Monzo - DOXLON - Presentation 📺

**URL:** <https://community.monzo.com/t/solving-network-challenges-at-monzo-doxlon-presentation-tv/7359>\
**Category:** Monzo Chat\
**Created:** [1 February 2017 09:20 UTC](https://community.monzo.com/t/solving-network-challenges-at-monzo-doxlon-presentation-tv/7359 "2017-02-01T09:20:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexs](https://dub1.discourse-cdn.com/monzo/user_avatar/community.monzo.com/alexs/32/2443_2.png) [@alexs](https://community.monzo.com/u/alexs)\
**Post date:** [1 February 2017 09:20 UTC](https://community.monzo.com/t/solving-network-challenges-at-monzo-doxlon-presentation-tv/7359/1 "2017-02-01T09:20:07Z")

</div>

@anon77247897’s presentation from last week’s Dox London event.

> On the one hand, Monzo’s backend is composed of hundreds of microservices running in Kubernetes. On the other, banks need to interconnect to hordes of legacy systems, often involving physical kit and leased lines. This presents an interesting networking challenge. Oliver Beattie, Head of Engineering, goes into detail about how Monzo has designed its network architecture, how they secure it, and lots of lessons learned along the way.

[![](https://global.discourse-cdn.com/monzo/original/3X/5/9/59c65a5b4f7de0ce8df4d53a71a7781229240785.jpeg "Solving Network Challenges at Monzo, a Banking App") ](https://www.youtube.com/watch?v=nuli2rcLxpk)

[http://www.slideshare.net/dataloop/network-challenges-at-monzo-a-banking-app](http://www.slideshare.net/dataloop/network-challenges-at-monzo-a-banking-app)

There’s a summary of the event & the other talks from the evening [here](https://blog.dataloop.io/doxlon-january-2017).