The nature of the way Monzo operates makes this much less likely to occur.
And if it does happen, the nature of how they operate means it should be significantly faster to resolve. Particularly because there is no reliance on a third party
Pedantically, they'd still be reliant on MasterCard's systems, and their connectivity to them, but if MasterCard went down Monzo wouldn't be the only one with problems.
Care to explain why? What is this "nature of monzo operation" that solves errors quicker?
If anything, a small startups who has to redo everything from scratch with limited resources seems like there is huge room for errors, and not many people to support and fix them 24/7.
They are a tech company first, financial one second. They made a decision very early on to build everything from scratch in the "right" way, pretty much no matter how long it would take or how much effort would be involved.
Their systems are incredibly stable. In fact, I don't think I can recall a single bit of downtime which was actually down to their system since November 2015 when I joined.
In the case which happened here, some kind of unexpected migration gone wrong - Monzo's systems are highly decoupled and separated. So any given database issue will only affect that given service. As each service is so simple and contains relatively little code, working towards a resolution can be achieved significantly faster. The smaller scope of responsibility also means that a mistake is less likely to happen in the first place.
> Their systems are incredibly stable. In fact, I don't think I can recall a single bit of downtime ---which was actually down to their system--- since November 2015 when I joined.
Downtime is downtime.
Ignoring and shifting the blame to third parties will not fly with customers who are unable to buy their groceries. Just saying ;)
And if it does happen, the nature of how they operate means it should be significantly faster to resolve. Particularly because there is no reliance on a third party