Name: 雲計算 - 介紹 (Cloud Computing - Introduction)
Uploaded: 2021-01-14T10:44:12.000Z
Duration: 1 h 10 min 48 s
Description: 【看影片學英語】數萬部 YouTube 影片，搭配英漢字典即點即查，輕鬆掌握單字發音與用法，長久累積看電影不必再看字幕。

please go to the line the computer guy dot com, in order to view schematics, code and Maur for the projects that you are learning about.

I'm going to give you an introduction to cloud computing.

So Cloud computing is one of those things.

But then people get very confused with all of the different terminology, and then it kind of sort of makes their head explode.

The important thing to understand when you're dealing with cloud computing is you need to be looking at solving problems, figure out what your problem is, and then you figure out what technology you were going to use to solve that problem.

Ah, lot of times people, when they get into cloud computing, a hyper focus on specific technologies, whether it's virtual is ations or sands platforms, a service serverless, architectural, service oriented architecture, they focus on some specific thing, and it's kind of what they say.

You know, if you've got a hammer, everything is a nail.

That's what a lot of cloud technicians look like.

They understand one type of cloud technology and they're gonna you're just gonna bang the hell out of any problem that they find with it.

So the important thing that I really want you to be thinking about when you start thinking about cloud computing, you need to look at what your problem is.

You need to look at what your requirements are, and then you go out there and you find a solution.

Maybe some very expensive internal private hybrid cloud that's gonna cost millions and millions and millions of dollars.

Or it may be spending up some some virtual instance on something like Digital Ocean that's gonna cost you $5 a month.

The important thing to understand is to be thinking about what are you actually trying to accomplish and then figure out the tool for that?

So one of the big things that you need to be thinking about when you start thinking about cloud computing is now in the modern world with cloud computing.

When you think of service is even when you think of servers, you now need to no longer think about a specific box that you can literally 0.2 and says that box does X so for me as somebody who got his M c s e literally NT 4.0, back in like the 99 2000 time frame.

When we had servers, we had servers that offered specific service is to our client computers.

So if you're looking at something like active Directory, if you're looking at something like databases, if you were looking at something like email, you could walk into my server room and I could say That's the active directory server and that's the exchange server and that's the database server, and that's don't ask me about that.

That one doesn't a lot of stuff for the company, but we're just as a mess.

But the important thing, the important thing to realize is not that long ago is that if you were offering a service is to client systems or you're offering service is to the user, you could literally go and you could point at the physical machine, and you could say that machine does X, Y and Z.

The thing is, to realize with cloud computing is that is not the case.

You do the configurations you load the configuration somewhere, and then basically what you can say is it's kind of like, you know, one of those well, in that direction, right, like our service is run on Amazon.

I probably might not even know what state the server is it quite literally, or even again with private clouds.

When you think about private clouds, one of big things with private clouds, you can do all these cool things with what's called clustering.

So what you have is when you have clustering, as you have multiple physical machines that are all able to communicate with each other, and then what they're able to do is they're literally able to in real time to move around things like Tasks, Service's virtual machines, the whole nine yards to whatever physical hardware is the most appropriate.

Let's save VM where hyper visors, so via more hyper visors, a type of virtualization technology, so I could have 10 you nosy on servers with VM wear hyper visor installed on them, and those 10 physical machines are responsible for however, many of virtual machines, then I have running well.

The thing is, is VM wear can automatically move instances of virtual machines around as as required.

So let's say you have something like a video encoding, so you have a server that's responsible for video.

Now, most of the time right that server isn't doing is literally not doing anything right.

It's it's running because it needs to run.

But otherwise it's not really using any ram.

It's not really using any storage, and it really isn't using a CPU right.

It's just is just a server in the state of waiting for a client to request something for it.

So if you have a cluster of virtual machines, what can happen with the M, where museum, where you can put the instance of that encoding server onto a specific machine that doesn't have a lot of resource, is doesn't have a lot of capability because it doesn't need a lot of resurfaces capability?

Now imagine it's 10 o'clock in the morning.

Your video editors have finished with their their first productions for the day, and they're now pumping their video files to now be encoded.

What can happen is the The hyper visors are able to communicate and basically that instance of the machines to the instance of machine that's sitting on that very low resource server that physical hardware can now be automatically moved to, Let's say, a server that has 128 gigs of Ram PC.

I expressed solid state drives, you know, for eight cores eon processors, the whole nine yards.

So basically, as people need actually use that server to do video encoding, the instance of that server has now moved to that higher quality hardware.

It then does all the video encoding that is being asked to dio when it gets done with that, it might wait five or 10 minutes just to verify.

Nobody else needs its help anymore, and then after that, it gets automatically moved back.

So if you walk in and you have a private cloud, you have a V M where cluster and basically somebody asks you where is that encoder server running again, depending on the time of day, depending them alone, depending on your just like that rack, like literally just go.

I could figure it out if I really wanted Thio, but it's like it's running somewhere in the rack.

It might be sitting there up on that low resource system right now because it may not be being used or the video editors may be hammering the hell out of it.

And it's down on this higher and a server at the bottom that requires a lot of power.

And so that's one of the big things to be thinking about with Cloud Computing with cloud computing.

What we're really talking about is that you set up service is you make service is available to your clients and users, but you can't physically point toe a box and say that box is providing X y or Z service.

Once you start dealing with a cloud computing is that we start doing something called have distracting all the components of the server right, so back in the day and you would have a server and that server would have everything on it.

That visible server has a however much Ram has.

You then install an operating system onto that server.

All your service is on to that operating system, right?

So that physical box has everything that you need.

When the cool things that we could do is we can rip apart that entire concept.

And now the compute and the storage and even the networking could be ripped apart, and they could be interacted with as their own individual components in their own individual things.

We start talking about that work civilization cluster.

So let's say we have 10 hyper visors in a cluster.

Mother question that has to be asked is, Well, wait a minute.

If you have some server and has a lot of data storage, you can't just instantaneously be able to move.

Ah, 100 gigs of data amongst all of the systems.

Well, how that works is the virtual cluster that you have.

That's all the CPI that has the processors that has the ram that has those types of things.

But the actual storage distorted for the operating system most likely resigns and something called a sand a storage area network.

So basically, you have this cluster of compute here and then over here you have a cluster of story, so store it has now literally been separated from the compute, and so now you can interact with them separately.

And so that's one of the things that you you can also do in the cloud computing world.

Is your rip apart all of these different components of what creates a server, and then you can interact with them individually.

So that's one of things is very interesting, something called a server, less architecture.

That's one of things that all the cool kids we're looking at right now we're literally It's really cool.

You can write scripts, and then the actual compute is offered to you just as a service just like D A.

N S is so you can literally actually call compute on When you call Compute.