Building a Bank with Kubernetes [slides]

Post by KirinDave » Mon, Oct 24, 2016, 4:04 PM UTC

tluyben2 wrote: post #23

obeattie wrote: post #19

Earlier quoted context omitted.

>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 of FUD about how you can and cannot build your technology as a regulated entity – and in particular as a bank. In reality, close to 100% of requirements from a regulator will tell you…

> I just want to say that I think there is a huge amount of FUD about how you can and cannot build your technology as a regulated entity – and in particular as a bank. In reality, close to 100% of requirements from a regulator will tell you _what_ you must build, not _how_ you must build it. Even then, especially in terms of resilience and security, they are almost always a subset of our own requirements. Having work…

Post by obeattie » Mon, Oct 24, 2016, 4:15 PM UTC

tonyhb wrote: post #76

obeattie wrote: post #10

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 aside, I'll also be giving a longer talk at Kubecon going into more detail on some of this stuff :-)

If K8S secrets management is storing them in plain-text in etcd how do you go about making it actually secure for a bank?

Post by snowwrestler » Mon, Oct 24, 2016, 4:38 PM UTC

lgieron wrote: post #67

snowwrestler wrote: post #65

Earlier quoted context omitted.

Why would eventual consistency be unacceptable in a banking system? In my experience people interact with social media on far shorter time scales than their banks. When they post a new Instagram photo, they expect that their friends will see it basically instantaneously. In comparison, when people use their debit card at CVS, they're not expecting anyone to log into their bank account seconds later and see the charge…

If your data is only eventually consistent, then DB node A can have your bank balance at $x for some time still, while it is already $0 at on node B. Then, if some operation (say withdrawal) is checking the balance with node A, then you have a problem.

Post by timothyb89 » Mon, Oct 24, 2016, 4:48 PM UTC

runeks wrote: post #33

harshreality wrote: post #4

Earlier quoted context omitted.

% youtube-dl 'https://skillsmatter.com/skillscasts/9146-building-a-microservices-with-kubernetes' [generic] 9146-building-a-microservices-with-kubernetes: Requesting header WARNING: Falling back on generic information extractor. [generic] 9146-building-a-microservices-with-kubernetes: Downloading webpage [generic] 9146-building-a-microservices-with-kubernetes: Extracting information [vimeo] 188042022: Downloading web…

Cool! Although, seems like "youtube-dl" may not be the right name for that app anymore.

Post by geodel » Mon, Oct 24, 2016, 5:16 PM UTC

obeattie wrote: post #84

KirinDave wrote: post #78

Earlier quoted context omitted.

Yes but that may or may not mean direct involvement with regulators. For small companies it's really hard to tell where they are in the process.

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 want.