6 ms·
Building a Modern Bank Backend
- cm3 10y agoGenuine questions: Is it commonplace for a bank to be a British Ltd, and are they part of a separate banking emergency fund to accommodate for that because they have a banking license? Also where do I have to look to find a real world address for Focus FS Ltd (company behind Mondo)? Looked around the internet after finding nothing on monzo.com. I know startups do not list contact info these days, but whois info is also opaque. I'm asking this because they advertize themselves as a modern bank, but I cannot find a real world address after 5 minutes of searching.
- JazCE 10y agohttps://beta.companieshouse.gov.uk/company/09446231 https://beta.companieshouse.gov.uk/company/09446231 basically all companies should file with companies house...
- maxblackwood 10y agohttps://beta.companieshouse.gov.uk/company/09446231 https://beta.companieshouse.gov.uk/company/09446231
- grahamel 10y agoYou can find Focus' details at companies house, https://beta.companieshouse.gov.uk/company/09446231/filing-history https://beta.companieshouse.gov.uk/company/09446231/filing-h... Bit more about Mondo/Monzo on wiki https://en.wikipedia.org/wiki/Monzo_(bank) https://en.wikipedia.org/wiki/Monzo_(bank) (they recently change the bank name) Initially they only offered prepaid cards while they waited for their banking licence. They're not covered by the Financial Services Compensation Scheme (FSCS) at this point but will be when they start to offer current accounts. They've recently got their (restricted) banking licence so they'll be part of the FSCS fairly soon. Part of their restrictions is that they can only hold up to £50,000 ($65,000) in customer deposits, the FSCS covers up the 75k in savings so customers money is protected. (http://uk.businessinsider.com/uk-digital-bank-mondo-lays-out-plan-to-get-full-banking-license-2016-8 http://uk.businessinsider.com/uk-digital-bank-mondo-lays-out...)
- obeattie 10y agoAs others have mentioned, you can find it on Companies House, or on the the FCA (Financial Conduct Authority) register: https://register.fca.org.uk/ShPo_FirmDetailsPage?id=001b000002syvKiAAI https://register.fca.org.uk/ShPo_FirmDetailsPage?id=001b0000...
- pjc50 10y agoI'm not sure what other structure a UK bank could have, other than Plc?
- andrewingram 10y agoTheir office is 50m down the street from mine :)
- jwr 10y ago> we’ve built our backend as a collection of distributed microservices I hope I will never have to rely on a bank that uses this architecture. It seems they are vastly underestimating the complexity of distributed systems and the range of their failure modes. It's all cool if you're building a web site, less so if it's about your money and being unable to pay at a gas station.
- simonhorlick 10y agoHaving worked in the industry, most top tier investment banks run on microservices, some for over a decade. Just because microservices is the new buzzword doesn't mean it's suddenly a bad, or risky idea. I don't know about the backend state of modern retail banking, but I'd be surprised if this wasn't also the case.
- collyw 10y agoThe one I used to work for was all heavyweight relational databases. Admittedly this was nearly ten years ago.
- threeseed 10y agoMost enterprises/banks still have their Teradata or Oracle EDW at the heart of the company. It's just that rather than have a single monolithic app in front of it they have broken it up into a suite of smaller, independent services. And many of those services will have their own database which contains a transformed, optimised slice of the total EDW data.
- dx034 10y agoAs far as I know that only applies to some front end system, but not for anything accounting related. Even modern trading and accounting software has a big relational database somewhere to ensure integrity of the inventory. Everything around that (trading models, development, research systems, reporting) can be microservices, but it will all rely on the core system.
- threeseed 10y ago
- ddorian43 10y agoWe knew from the start that we would be the next ((facebook+google-apple) ^ spacex), that's why we started with distributed microservices, (you can't ignore docker these days on hn frontpage, you HAVE to use it), golang + node.js + kafka combo. We're not in beta yet and we have 150+ services, isn't that insane right! We need a protocol for rpc, http+json was the slowest one --> clear winner. Everytime we need a new function, we can make it a service and make it distributable on our polyglot (because why not!) docker infrastructure behind http load balancers + json data-type and make it infinitely scalable!
- blibble 10y agoI think Josh Berkus said it best: https://youtu.be/nPG4sK_glls?t=47 https://youtu.be/nPG4sK_glls?t=47
- obeattie 10y agoAuthor here. We are in beta and have about 40,000 cards issued to customers in the UK, with a waiting list of about 200,000. I think we have good reasons for making the architectural decisions we have made, some of which are laid out in the post, but perhaps I did not explain them in enough detail. For example, we chose HTTP as our RPC protocol because it is widely supported in many languages, and has mature support in Finagle. HTTP/2 fixes most of the performance issues with HTTP, and we have options (eg. to use mux) if we still find there are performance problems – although at the moment, we are quite happy with performance.
- threeseed 10y ago
- lordnacho 10y agoSounds very impressive. It'll definitely scale if they can somehow build it with 3 coders. I would have thought you could start with a bog standard CRUD setup. How many customers are they serving at the moment? How many queries is one customer going to make each day? What part of a bank are they actually trying to make? Just current accounts? Or multi asset market making? The requirements are quite different. Also, on the business side, why does the UK market need another bank? It's a totally commodity service. Why would I want to use this bank? Do they offer something better?
- dbbk 10y agoJust current accounts. And yes, the UK does need a new kind of bank. Monzo's USP is that their technology is modern and built from the ground up. For the end user, this means you get push notifications of card transactions instantaneously. You can freeze and unfreeze your card instantaneously. The Monzo app uses your phone's location to determine when you travel to a new country, and doesn't block your card for suspicious activity as a result. It gives you realtime currency conversion for your transactions. The app allows you to budget your money, and categorise where you spend it. And more. -edit- Oh and I forgot to add, they offer a complete API, so you or third party developers can build on top of your financial data. No other bank offers this today.
- saiya-jin 10y ago> Oh and I forgot to add, they offer a complete API, so you or third party developers can build on top of your financial data. No other bank offers this today. this part ain't completely right - all current banking backends on the market offer instant messaging integration, otherwise they wouldn't be bought. it's not straightforward API calls directly in the backend (which some would prefer to not expose directly anyway). a bit of glue code is required but this is how in the moment these systems evolve to conform to ever changing regulations for example. otherwise banks would have to shut down
- dbbk 10y agoPublicly accessible API then.
- gaius 10y agoLarge internet companies like Amazon, Netflix, and Twitter have shown that single monolithic codebases do not scale Except Google does have a "single monolithic codebase", so actually, the jury's still out on that one. Personally I wouldn't bet the farm either way at this point.
- ddorian43 10y agoI think Google has 1 code repo. But runs different services (note missing "micro" there).
- abritishguy 10y agoGoogle has one repository, not one monolithic codebase.
- rco8786 10y agoHeh. No. They keep the code in a single repository but it by no means a monolith. Kubernetes is FROM Google. Along with some of the most advanced distributed systems implementations in the world.
- jen20 10y agoMonorepo != Monolith.
- raesene6 10y agoI'd read this article and something about it bothered me, took a while to put my finger on it. To me creating a back end banking system using a load of software that's very new and still very much developing is a risky move. Once they're in production bank back ends tend to be around for a LONG time (in my experience in UK FS there were a load of old back-end systems that were maintained out of necessity as they were too expensive to re-write and the product they supported was still in use) To me banking back-end systems should be boring from a tech perspective. Use well known components where the limitations and downsides are well known, and also if it were me I'd use components that I could get a support contract for. You don't want to be relying on open source support at 3am on a Sunday when you hit some bug or other and the FCA is breathing down your neck to get your transactions processed in a timely manner.
- mataug 10y agoOr have some kid discover a memory allocation bug and fake a couple of thousand pounds into an account.
- MichaelBurge 10y agoI'm not saying it can't happen, but double-entry accounting will usually detect it and the ACH system* will usually let you reverse it. * Or whatever the UK equivalent is.
- collyw 10y ago"Large internet companies like Amazon, Netflix, and Twitter have shown that single monolithic codebases do not scale to large numbers of users". Strange that because banks have been using relational database technologies for that task for years.
- threeseed 10y agoYes and many are trying to move away from them because of the cost. You are aware that Teradata servers cost in the order of 30K per node and support costs god knows how much. Any internet company wouldn't even make it past day one if they need to sink a few hundred thousand just to get started.
- DanielBMarkham 10y agoIntuitively I like this -- hits all the good buzzwords and has a ton of good things going for it. I was especially impressed that they're possibly heading towards a Simian Army situation. To me this is the only logical way to deploy infrastructure in a modern setting. I'd sure like to look under the hood, though. Most interesting was "...Deploying Kubernetes in a highly available configuration on AWS is not for the faint of heart and requires you to get familiar with its internals, but we are very pleased with the results..." Wonder how much pain and suffering there was getting this to where they wanted it. The only part I was concerned about was 150 microservices so early in the game, moving to message queuing while still very small, and the RPC/locking stuff. Smells like over-engineering. But hey, I'm not there. There's a ton of stuff that goes into making decisions like that. Thanks for the story!
- collyw 10y ago"hits all the good buzzwords" You see that as a good thing?
- DanielBMarkham 10y agoNot by itself. By itself it would be counter-indicative. But assuming good intent, I felt the buzzword-compliance indicated an understanding of the deeper issues involved. It's a difficult situation. I don't want to spend all day reading an article defending CoreOS. But if you throw that buzzword out, I'm assuming you've had some good discussions about your OS selection and could provide that depth if needed. Same for the others. They're not right or wrong choices, but I'm assuming they're there not because the team wanted to be trendy, but because there was real architectural need. If we're discussing architecture, by necessity we're going to have to skim over a lot of stuff. I was okay that given the team's desire to prevent a single point of failure that the pieces listed worked towards that goal. It's very easy to put too much stuff into a system. It's also very easy just to do trendy stuff without thinking through the consequences. I'm giving them the benefit of the doubt until shown otherwise -- and at the end of my comment I was clear about what some of my concerns were.
- dharma1 10y agoOh, they're called monzo now? I guess changing one letter was the cheapest in terms of logo redesign :) I think what they are doing is bold (especially in terms of security, I think their head of security role is still open?) but ultimately the right thing to do for a truly disruptive banking startup. I don't think it's possible/easy to bring the features people want from modern banking software front end (free text search through transactions etc), with a legacy banking backend.
- ryanhuff 10y agoWhy not? I've seen it done.
- deleted 10y ago[deleted]
- saiya-jin 10y agoit's entirely possible to have a classic PL/SQL banking backend running on some crazy cluster, and having Angular.js/Node.js frontend with good ol' Java middle tier with all the UI goodies that you expect in 2016. I know since right now I am customizing one of those for my employer.
- fixxer 10y agoThere are tons of opportunities to improve banking and credit, but these overarching statements about new technology yay and micro services good and batch processing verboten... Ugh, total jargony bullshit. Building the best X is about using the best tools to do what X needs. Not everything craves massive scale and a TON runs better on a well provisioned RDB! Want to revolutionize banking? Fine, but don't forget the fucking CAP theorem when you're storing my cash.
- jhuckestein 10y agoI work at Monzo. I agree that using microservices and kubernetes is not what allows us to provide a good user experience. We could provide the same user experience if we had built everything on rails and postgres. In fact, that would have been much easier. The reason we are investing so heavily in a rock solid platform is that we want to still be able to offer the best possible user experience in 10 years time. This is what we mean when we say we want the platform to be "extensible". Many large banks IT systems are not extensible, in the sense that it is very expensive to make changes. Take, for example, the ability to freeze a card in the app at the tap of a button. A friend at RBS told me that they considered this feature many times, but it took a long time to work out which 20 IT systems would need changing and some of them had been under change freeze for a few years. So eventually the idea was discarded as too expensive. The freeze card feature would be easy to implement for a startup, regardless of their stack. The key is to still be able to implement such a feature easily in 10 years time :)
- fixxer 10y agoI'm sure you mean well. You need to pare back the jargon and focus these blog posts on user experience, IMO. As an engineer dealing with all the usual bullshit from higher ups that learned a new buzzword and have to have it right now (even though it doesn't do what they think it does...), an article like this is always going to get a response like mine. And on this forum, I'm not alone.
- sirgiganticus 10y ago
- asimuvPR 10y agoWhy not java?
- dx034 10y ago>Large internet companies like Amazon, Netflix, and Twitter have shown that single monolithic codebases do not scale to large numbers of users, and crucially large numbers of developers. How is that true? These companies have shown that you can scale well if you don't have monolithic approaches, but that doesn't mean that you cannot scale if you have one. Just because someone is successful by using approach B doesn't make approach A unsuitable. Quite the opposite. Some banks handle more than a billion transactions per day on monolithic infrastructure (think of big investment banks with a sizeable amount of trades per day). It's very costly, but it does work reliably. EDIT: One thing I don't get: Most banks use a central database somewhere because you need to have accounting values that you can rely on (e.g. how much money you have on your account). How do they do that? They must use some synchronization with locking that works across all services which rely on them, but how will that scale well when they get dozens of transactions per second? How do they guarantee the integrity of their data?
- obeattie 10y agoI'm the post's author. The key point I was trying to make was not that monolithic systems cannot handle the throughput, but that they become more and more difficult to extend and maintain as they grow. None of the companies mentioned started out with a microservices architecture – they moved to them (at great expense) when they found development difficult to scale.
- dx034 10y agoThanks for the answer. I'm not against your approach, just curious if it will work. How do you handle synchronization for large numbers of users? Many bank related transactions require some kind of locking (getting account balances, authorizing transfer, ...), doesn't that lead to a high probability of deadlocks at some point?
- mping 10y agoGeez, all the haters here. I would argue that as long as you don't actually lose any customer's money, its OK to screw up once in a while. My e-bank site its down once a week for deploys or so, my bank's mobile app didn't to certificate pinning, and they are still operating. Actually I believe CAP isn't actually that relevant, because most money is transferred and there are double ledgers for that, which for sure isn't fully consistent. As for the paid software and support, its a crap reason. The support guy isn't omnipotent, at best he's seen the issue you're having and will help you faster. If you have paid software and you have downtime because of them, good luck trying to get money from them. And there's nothing wrong with microservices, as long as you don't need to call a bunch of them to update my balance. I don't care if I try to change my address and the service is unavailable, or if I don't receive a weekly notification. Its much better than having e-bank site downtime because they want to deploy a new version of the webapp. As long as you maintain account balance integrity, I'm sure you guys will do just fine. All the best
- raesene6 10y agoit's nice to hear that you're a flexible and accomodating customer who's not adverse to companies having some IT issues. Unfortunately banks in the UK are regulated by the FCA and they are more than a little picky about that kind of thing. As an example RBS were fined £56 million for an outage a couple of years ago (https://en.wikipedia.org/wiki/2012_RBS_Group_computer_system_problems https://en.wikipedia.org/wiki/2012_RBS_Group_computer_system...)
- mping 10y agoThat didnt' seem that it was a minor outage. Anyway, these things apparently happen even without microservices or kubernetes. Time will tell.
- yid 10y ago> Large internet companies like Amazon, Netflix, and Twitter have shown that single monolithic codebases do not scale to large numbers of users, And yet, both Facebook and Google have large, monolithic codebases.