Here's the live request flow on a large subset of the 1500+ microservices on the @MakingMonzo Platform. A lot of things are involved in running a bank!
If you used the @monzo app at around 3pm today, you might be represented
pic.twitter.com/mkublWrRCV
Also, I'm interested in whether this makes it difficult to add new features if the features span multiple squads? Or perhaps you have a way to manage this - like, creating a composite team with knowledge of the necessary services.
-
-
On the face of it, we work hard to making banking as accessible and simple as possible. We deal with the complexity so customers don’t have to This means we do a lot of the heavy lifting. Computers are good at doing that in a reliable fashion
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If features span multiple squads, we take a step back and write Proposals before we go into implementation. This opens it up for critique and feedback. One benefit of having smaller services is you can get context really quickly.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For example, last week I shipped changes in quite a few key services such as our account service and our lending services. I was able to get context really quickly. It’s all about having common abstractions and good documentation. Keep code as self documenting as possible.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.