Long-time lurker, first-time poster!
This is a question about Monzo’s architecture, not a question relating to the public API
I’m currently designing a bespoke piece of software and we’re adopting a microservices architecture running on Kubernetes (AWS EKS).
How does Monzo route ingress traffic? I’m concerned that exposing 1 service via a loadbalancer and just tagging a route is going to become unmanageable. e.g ‘api.monzo.com/customer/1’ Do you use an API gateway such as Gloo or Ambassador?
Luckily, all ingress/egress traffic will remain in our cluster so there is no requirement to even do this but I just wanted to get other opinions.
We’re planning to use Istio as a service mesh and Calico policies to restrict pod-to-pod access.
Whilst planning, we think that we’ll deploy 500+ services and I read somewhere that Monzo publishes many more and still seems to be really organised.
If this question is out of scope, I apologise! Please delete/close the thread.