obeattie

12 ms·

61.
by obeattie 10y ago
I'm the Head of Engineering at Monzo. We don't use floating point at all in our core banking systems, which are all written in Go by our own engineering team :)
62.
by obeattie 10y ago
Regardless of how you feel about Google's motivations, this is a pretty dismal commentary on the state of browser interoperability.
63.
by obeattie 10y ago
Yes. "We've identified the issue as high error rates with S3 in US-EAST-1, which is also impacting applications and services dependent on S3. We are actively working on remediating the issue."
64.
by obeattie 10y ago
Best thing about incidents like these: post-mortems for systems of this scale are absolutely fascinating. Hopefully they publish one.
65.
by obeattie 10y ago
The only reason to consider Cloudflare, for us, is DDOS mitigation.
66.
Monzo’s Response to Cloudbleed(monzo.com)
151 points by obeattie 10y ago|59 comments
67.
by obeattie 10y ago
Commenting is painful.
68.
by obeattie 10y ago
At Monzo where I work, we use Dropbox Paper quite extensively for internal RFC's in the engineering team. We'd probably prefer to use a Google product since the rest of the company uses Drive so heavily, but Docs is simply atrocio
69.
by obeattie 10y ago
I imagine what is considered an "enticing" cover for a book aimed at scientists and engineers has changed a bit between 1997 (when this was published) and now.
70.
by obeattie 10y ago
Monzo | Full time | London/remote | Visas sponsored | https://monzo.com/careers/ At Monzo we aim to build the best current account in the world. We are always keen to hear from capable, creative engineers who want
71.
by obeattie 10y ago
We're _very_ directly involved with regulation, and with regulators :-) It's a very important part of our business, so we put a lot of effort into ensuring that we please regulators _and_ that we run our business in the way we wan
72.
by obeattie 10y ago
We don't store things that are actually secret, as k8s secrets ;-) Hashicorp Vault is quite good at this.
73.
by obeattie 10y ago
To be clear, we (Monzo) are not writing banking software in PHP, or using MySQL.
74.
by obeattie 10y ago
Because of its disk layout, Cassandra is truly excellent at time-series, append-heavy data. In our setup, the data is partitioned by time bucket and n number of labels (one of which is the request ID). We may unify the two at some point, bu
75.
by obeattie 10y ago
This is great feedback – thank you. A lot of the feedback from my blog post a month or so ago was that the "why" was not clear enough, so I guess I focussed more on this. Now I've (hopefully!) covered that better, I agree tha
76.
by obeattie 10y ago
>what really limits most financial institutions from embracing a lot more modern tech is their core systems of record AND the acceptance of said systems by their governing agencies. I just want to say that I think there is a huge amount
77.
by obeattie 10y ago
Good question. We have a couple of approaches to this: * Every request that comes into our system is assigned a unique ID, which is propagated on every downstream call and returned in a response header. When logs are emitted during request
78.
by obeattie 10y ago
Author of the talk here. Happy to answer any questions anyone has. This post also contains more info on how we build our systems: https://monzo.com/blog/2016/09/19/building-a-modern-bank-bac... And as an
79.
by obeattie 10y ago
Almost all of them interact with other services to do something or other.
80.
by obeattie 10y ago
I'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 mentio
81.
by obeattie 10y ago
As 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=001b0000...
82.
by obeattie 10y ago
Author 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
83.
Building a Modern Bank Backend(monzo.com)
11 points by obeattie 10y ago|1 comments
84.
by obeattie 10y ago
Potentially; we don't have many remote employees yet (but we'd love to in the future) so we're still finding our way with it.
85.
by obeattie 10y ago
I'd say it's unlikely, but anything is possible.
86.
by obeattie 10y ago
Absolutely. We don't have an ad up for internships specifically (we probably should!), but you can fill out the backend application and mention you're looking for an internship :)
87.
by obeattie 10y ago
Monzo | Backend Engineer | Full time | London or Remote | https://monzo.com/ At Monzo we aim to build the best current account in the world. We are always keen to hear from capable, creative engineers who want to help us ac
88.
by obeattie 10y ago
On Mondo, there simply are no passwords at all. Instead, when the user wishes to log into our first-party apps, we send a login link to their registered email. We'll almost certainly add additional required factors to this process (eg.
89.
by obeattie 10y ago
Why? In order to have a Mondo account, the user must have our app installed.
90.
by obeattie 10y ago
In the proposed implementation above, the _only_ piece of information that a user enters inside the web view is a username. The user must then use the native Mondo app on a previously-authenticated device to complete the OAuth flow. The Mon

More ›