Live data from Hacker News

Building a Bank with Kubernetes [slides]

community.monzo.com

1–10 of 106 posts

Re: Building a Bank with Kubernetes [slides]

#4
post #3

Is there a video available elsewhere? Last I checked, it wasn't possible to download those from SkillsMatter.

    % 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 webpage                                                             
    [vimeo] 188042022: Extracting information                                                          
    [vimeo] 188042022: Downloading JSON metadata                                                       
    [vimeo] 188042022: Downloading m3u8 information                                                    
    [download] Destination: Meetups_Oct19_19-43-44-188042022.mp4                                       
    [download]   7.9% of 152.75MiB at 82.49KiB/s ETA 29:05

Re: Building a Bank with Kubernetes [slides]

#5
It can be called: "How we built 'x' with Kubernetes".

Really the only thing that is specific to a bank (as I see it) is that they use separate linkerd in order to do the secure stuff. Which is essentially what banks have been doing for ages.

I commented before on how Kube has just taken over and beat mesos/marathon stack. This talk is an example to that. You can see how many people jumped on the Kube stack and running successful deployments on it.

Re: Building a Bank with Kubernetes [slides]

#6

It can be called: "How we built 'x' with Kubernetes". Really the only thing that is specific to a bank (as I see it) is that they use separate linkerd in order to do the secure stuff. Which is essentially what banks have been doing for ages. I commented before on how Kube has just taken over and beat mesos/marathon stack. This talk is an example to that. You can see how many people jumped on the Kube stack and runnin…

But what about "Big Data" workloads? Running Spark or Cassandra clusters say? My understanding is that having a custom scheduler makes mesos more attractive for those tasks? Has your experience been different?

Re: Building a Bank with Kubernetes [slides]

#7

It can be called: "How we built 'x' with Kubernetes". Really the only thing that is specific to a bank (as I see it) is that they use separate linkerd in order to do the secure stuff. Which is essentially what banks have been doing for ages. I commented before on how Kube has just taken over and beat mesos/marathon stack. This talk is an example to that. You can see how many people jumped on the Kube stack and runnin…

Disclosure: I mainly use DC/OS mesos myself. I've evaluated k8s for our use case and didn't find it was quite what we were looking for. Our customers and stack are mainly JVM based. We do on prem deployments not cloud where GCE is already doing pretty well. We also mainly work with the microsoft side of things (azure,enterprise stuff)

Not convinced of this. Direct mesos and yarn integration with spark (not to mention a lot of the software already being built on top) is going to keep mesos/marathon relevant for a long time. It's definitely better for big data workloads.

I think a lot of startups will jump to this for sure. Many startups don't actually have big data stacks and prefer to use go based stuff (mainly because it's simpler). In that case k8s makes sense for that.

A lot of these companies will likely prefer DC/OS and mesos/marathon because they have in house zookeeper expertise already. ZK is a dependency for much of the big data ecosystem as well a kafka and mesos.

The synergy is a lot better.

That being said: Many here will disagree. I definitely think k8s is winning developer mindshare overall, but I don't think it will have 100% of the market.

Re: Building a Bank with Kubernetes [slides]

#9

It can be called: "How we built 'x' with Kubernetes". Really the only thing that is specific to a bank (as I see it) is that they use separate linkerd in order to do the secure stuff. Which is essentially what banks have been doing for ages. I commented before on how Kube has just taken over and beat mesos/marathon stack. This talk is an example to that. You can see how many people jumped on the Kube stack and runnin…

But what about "Big Data" workloads? Running Spark or Cassandra clusters say? My understanding is that having a custom scheduler makes mesos more attractive for those tasks? Has your experience been different?

Personally I always ran big data on Amazon stack so never really needed that ability

Re: Building a Bank with Kubernetes [slides]

#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 :-)

Post reply on HN