Name: Microservices in the Cloud with Kubernetes and Istio (Google I/O '18)
Uploaded: 2018-08-22T21:38:29.000Z
Duration: 38 min 1 s
Description: Thousands of YouTube videos with English-Chinese subtitles! Now you can learn to understand native speakers, expand your vocabulary, and improve your pronunciation...

Today, I want to talk to you about microservices

So I'm a developer advocate on the Google Cloud.

I've been working with Kubernetes for the past three

And Istio is the next new hot thing coming out,

Because we all know microservices are awesome--

when you have a traditional application, like a monolith,

You would have all the code in your one app.

so you have different classes that do different things.

But at the end of the day, it's like one big program

And there's a lot of advantages to doing this monolithic type

of development-- it's easier to debug, it's easier to deploy.

You just have one thing, you just push it out,

and you have a very small app, it's really easy to do.

comes when your app starts to grow a little bigger.

But you still have one app that's doing all of it.

So any time you want to make a change in invoicing, that

means you have to redeploy the whole thing,

And maybe the invoicing part is really good to be done in Java,

the ETL pipeline you want to use Python, and the front end,

But if you have a monolithic app, you can't really do that.

You're kind of stuck into using one language.

So a team that wants to make an update to one little part

start to get really hairy really quickly.

that can be written in its own language, that can be updated

and deployed independently of the others.

And so this gives you a lot more agility, a lot more

flexibility, a lot more speed, and a lot more cool

And so you're like, yes, that sounds really good, why

Because once you start growing even bigger,

Honestly, a monolith would fall apart at this point too.

But even all the advantages of the microservice

because now you don't have just 20 services,

And how do you know which one talks to which one

and how the intricate spider web of connections even works?

gets sent to like 20,000 different microservices

And anywhere that chain breaks, your whole application

And so debugging this becomes super hard.

Deploying things, making sure everything's in lockstep

difficult to try to manage this huge stack of services.

Maybe, but we can use a lot of tooling to try

So let's use tools to automate this infrastructure components,

And so when you look at a monolith versus a microservice,

The difference is-- and unless you know something

that I don't, there is no tools out there

and can maintain a 2 million line Java app, right?

It's like some magic AI that can write code,

we'd all be out of jobs maybe in a few years.

But now we do have tools like Kubernetes, like Docker,

can automate infrastructure a lot more easily.

So a lot of the issues that we have with microservice

So let's take a look at some of those tools.

So how many people are familiar with Docker?

So for those of you who are not familiar with Docker,

Docker is basically a way to package your application.

So it doesn't matter if you're writing Node code, Python,

It doesn't matter if you have ImageMagick,