Cloud Native Computing Foundation KubeCon + CloudNativeCon North America 2016 (Seattle), 16 Nov 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Lightning Talk - Netflix OSS on Kubernetes by Christian Posta, Red Hat

Description

Lightning Talk - Netflix OSS on Kubernetes - Christian Posta, Red Hat

Some popular Netflix OSS components were created at a time when nothing better existed. Kubernetes bakes a lot of these concepts into the platform so that developers can simplify their applications regardless of language choice and still take advantage of things like service discovery, failover, loadbalancing, configuration, etc. So does Netflix OSS still have a place?

About Christian Posta
Christian Posta (@christianposta) is a Principal Middleware Specialist/Architect at Red Hat and well known for being an author (Microservices for Java Developers, O’Reilly 2016), frequent blogger, speaker, open-source enthusiast and committer on Apache ActiveMQ, Apache Camel, Fabric8 and others. Christian has spent time at web-scale companies and now helps companies creating and deploying large-scale distributed architectures - many of what are now called Microservices based. He enjoys mentoring, training and leading teams to be successful with distributed systems concepts, microservices, devops, and cloud-native application design.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

A

Thanks for coming, I'm gonna talk about Netflix OSS on kubernetes, my name is Christian posta I'm, a principal architect at Red, Hat I travel around North America, helping our enterprise customers build cloud native applications on top of kubernetes, the micro services style applications, and whenever you talk about micro services and especially enterprise, that's usually Java and our enterprise customers typically go down the path of looking at what the Netflix folks wrote, the they wrote an open source and and which is absolutely amazing, that they open sourced it and they and they're building a wonderful community around it.

A

They wrote these tools, things like hystrix and ribbon, and Eureka and Zul, and so on, and so on about five years ago, when they were going and bringing their applications into AWS. They built out things like distributed. Configuration service, discovery, load, balancing circuit breakers, those types of things to be run in Amazon's Cloud. The the thing that I really like about building applications on top of kubernetes is. It has a lot of that stuff built into where it comes out of the box.

A

So we don't have to you know, force our application developers to use Java, for example, just to use service discovery and the ribbon libraries we get that kind of stuff baked in for any programming language, and you don't have to use any specific types of client. So you can just use DNS and get service discovery, for example, and we don't want to we. You know you've heard that keep keep the infrastructure, boring kubernetes keeps distributed systems boring and has a lot of that those fundamentals baked in now.

A

What if you really want to use the same libraries on top of kubernetes, and you want to use things like history for doing circuit, breaking and so on? Well, in the fabricate community, we have a project called cube flicks, which allows you to use, reuse, the same api's and use the community service discovery and load balancing and health detection liveness probes, all that stuff, as is so it will use kubernetes under the under the covers. Has anybody heard of the fabricate community just curious, okay, awesome? So if I can it's gonna be tough?

A

Holding the mic microphone here, I'm gonna try to show a quick, quick demo. This talk is actually based on a blog post that I wrote that goes into a lot more detail. I'll go ahead and check out my blog that it goes into a lot more detail, but so we're gonna look at. We have an application deployed into our kubernetes cluster and Holly. Well, you can see that we have a hello world back-end service and the hystrix based application that will call into our simple hello world service.

A

But what we want to do is deploy the hystrix dashboard so that we can see those circuit breakers at runtime and use kubernetes discovery to find those circuit breakers well, which applications are running the circuit breaker to do that, we're going to install the history dashboard and the turbine dashboard using cube flicks if you come into fabric a and click on documentation, we'll go to the I'm running this on OpenShift OpenShift is awesome by the way click on open to manifest, and we have a lot of prepackaged applications that will run inside the open ship.

A

So what this is the the resource files, the ml resource files, we're going to take if I can find it the history dashboard and come over here and install it we're going to get the turbine dashboard?

A

Oh I, missed it right here.

A

And install it, and the last thing we're going to do is.

A

Service we're going to label our service history, we're going to enable history by labeling. Our service I'll show you here: OC label, hystrix hello world with history taught and enabled. Oh.

A

Thank you. Thank you. Thank you running out of time.

A

What did I do? Thank you, LC label. What did I do hystrix on the world and, like no pressure, haha am I doing it wrong? My mister screw it we're gonna, go over it, we're gonna. Do it this way, trying to be fancy edit? It.

A

Save it, it worked awesome. So now we go over to our historic stash board.

A

Right here, see it running. Ask it to mom to the streams, there's no there's no traffic going through. Yet so, let's go here and give it some traffic.

A

Traffic traffic traffic traffic- alright, now we come over here, where's hystrix. We should see some traffic now any any if I scale up, then those hystrix endpoints will automatically be discovered by using the kubernetes cue flicks discovery mechanism. So that's all I have thanks.