クラウドコンピューティング - はじめに (Cloud Computing - Introduction)

字幕表動画を再生する

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.
Welcome back.
So today is video.
I'm going to give you an introduction to cloud computing.
So Cloud computing is one of those things.
That's a very simple concept.
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.
The 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?
Not everything is a nail, I swear.
Thio.
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.
The thing is, back them.
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.
I had some ass, right?
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.
What's served?
What specific server runs that service?
I have no idea.
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.
So I could have 10.
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.
Cody.
Now, most of the time right that server isn't doing is literally not doing anything right.
It's just sitting there.
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 don't right now.
Right now.
I can't.
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.
I don't know.
That's kind of all automatically done.
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.
Thea other thing.
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.
So basically have a physical server.
That visible server has a however much Ram has.
A CPU has hard drive whole nine yards.
You then install an operating system onto that server.
You then stunts.
All your service is on to that operating system, right?
So that physical box has everything that you need.
So the storage is on there.
The processing is on there.
Everything is on there.
What cloud computing?
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.
So now it's storage again.
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.
Where is the story?
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.
How does that work?
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.
C p or D.
N S is so you can literally actually call compute on When you call Compute.
You don't necessarily know if it's a Lennox box, even in the compute or a UNIX box.
Even the compute where you gonna Microsoft windows box giving you compute.
Basically, what you're able to do is when you have scripts, you can have those scripts.
You say what?
That the input data is.
You say where you want that data output be again.
So if you're talking about something like video encoding and then what you could do is you can actually call to compute, and basically you can say Run, run this command against this file.
So let's say you want to encode a video in a 10 80 p.
So you can say is call this compute to encode this file in 10 80 p and out put it over here and then you're literally just calling.
And so again, it's not Windows.
It's not you, Nexus, not Lennox.
You're not worrying about all these things you're just able to actually call.
That is an individual service.
So these are some of the things that you need be thinking about in the cloud computing world, and that's why it's so important.
When you think about cloud computing, you don't try to hit it, Okay, because that's what so many people do, right?
So many people got their M CSC is they know how Windows 2012 server works.
They know how Lennox server works, you know.
And so then what they do is they try.
They try to take that they trying to take old school system administration and simply throw it on the cloud.
And that's just that's just foolishness would be like taking.
It would be saying if let's say, you know, the future of transportation is going to be aired.
Travel that would be like trying to throw wings literally on a car would be like going out my Ford F 1 50 trying to Super Blue Wings on and saying, Well, that's gonna be a flying car someday.
Like No, that's no.
You just superglued wings onto a truck.
That's probably a really bad idea, All right, well, you want to do if you want to create a new aircraft, is you actually build a new aircraft from the ground up, And so these are some of the things that you could be thinking about when you start looking at the cloud computing environment and how you're going to be interacting with the cloud computing environment.
So the first thing that we have to talk about is.
Where did the name cloud come from?
We start talking about cloud computing and we start talking about the cloud.
The question is, where did this terminology come from?
And so why is it important?
Don't understand that we have to go back to at least the 19 nineties.
We're gonna go back to the 19 nineties, goes That's where I started in the story.
It probably goes back a lot farther than that.
Back then, we were talking about the cloud a lot, but we weren't actually talking about cloud computing.
We were talking about the cloud in regards to networking.
So what I mean by that is so we were dealing with our own networks back then, right?
So you would have a router here.
And let's say the I P addresses 1 92 to 1 68 11 and under that router, you would have a server, and that would be, you know, not 10 1 92.1 68 1.10 And then that server, you know, under that would have a lot of different client machines, and they would all have their standard I P addresses and the thing is with this network right here.
We would know everything that was going on with this network.
We would know the modem or the and Tran.
We would know the rounder.
We would know the switch.
We would know the servers.
We would know all the host machines.
We would know the D, A, c P and the sub net masks.
We would know that D.
N s basically all this right here.
We would diagram out and we would know everything that was going on in our network.
Now let's say that this was a satellite office.
So let's say we have some kind of a company.
That company has one major headquarters, you know, back somewhere.
You know, they have a headquarters, and this is a satellite office that that's off on the other side of the country.
And so then, basically, we need to know how our host computers and how our servers from here will be able to communicate with the computers and the servers back at H.
Q.
Now at the H.
Q.
Again, we have a router there, and let's say they have a I P address.
Pretend 011 right, so that's there some that mask under that?
They have a whole crap ton of servers going on.
They have lots of networking equipment.
They have lots of host machines.
And they have, you know, they have lots of systems doing things.
And so we would also have all of this diagrammed out.
So we know all the servers.
We would know all the rounders.
We would know all the switches, we would know all the host machines.
All of this would be diagram to the nth degree.
And so, basically, what would happen?
And so if you have some client machine over here and it needs to communicate with a server over here, then we would be able to figure out what the routing path should be through our network for the satellite office.
And then once, once the traffic gets to the H Q once it gets attend, not one r Tenn 10.0 not one, not one.
Once it gets to their rounder, then the router and the network would then make sure that the packets the traffic gets routed to the appropriate surfer.
So basically, we understand how the traffic moves here, and we understand how the traffic moves here.
But the question is, is how do you connect the satellite office back to the headquarters?
Well, you have to connect it through what we called the club.
And so when we talk about the cloud back in the day, all the cloud meant, really, all the clouds still means is the Internet right?
So, basically, you have your external When you have your abs, are you have your external I P address.
Basically, that's the external row double I p address.
Your egg headquarters has its own external round herbal I p address, and what you do is you point the traffic at their external I p address, and they point their traffic at your external I P address.
Now the thing is, with the Internet, there's a lot of networking going on on the Internet.
Obviously again, there are what are called core routers.
There are course, which is there's lots of fancy, extraordinarily expensive equipment, and that extraordinarily expensive equipment is what routes the traffic from your satellite office, you know, over to the headquarters and then from the headquarters.
It routes it back to your satellite office.
Well, the thing is, with all this route these routers and this networking equipment on the Internet.
How traffic is modelled.
How traffic is moving really depends on what the current state of conditions are, right?
So again, there are literally thousands or millions of routers and pieces of networking equipment, uh, that the Internet service providers use.
And so what happens is they're all communicating to each other with something called rounding protocols.
And they're figuring out, you know what?
They're figuring out what the connection is working best, you know?
So this is a good connection, and they're figuring out what connections air dead.
For some reason, they're figuring out what connections are fast.
So let's say this one's fast.
They're figuring out what connections are slow and basically threw a rounding protocols.
All this networking equipment is trying to figure the fastest, most efficient way to get a packet from your external I P address to wherever you're going external.
I p address.
And the thing is, this literally this changes a moment by moment, just may change second by second.
So if I have traffic coming here, may bounce here, here, here, here, here, and then go over here and then traffic going back, make it bounced all the way up here and then down here and then traffic.
You know, two seconds later, we'll go this way.
Basically, this is all being dynamically around.
It s so that's where you here Sometimes when you hear about curious things with something called BTP, which is the routing protocol and for some reason, like entire cities, Internet traffic will randomly get routed to China.
Uh, yeah, that's because with how the communication happens with how the routing protocols work, basically dynamically, all of that, all the traffic is automatically being sent the way that the system thinks is most appropriate.
And sometimes it sends traffic through China.
And so the important thing to understand here, why we started calling this the cloud is because it really doesn't matter, right?
If I'm trying to get to this I p address and you're trying to get to this I p address, you don't really care if your traffic goes through this over down here or if it goes up and over.
Basically, you just say, OK, it leaves.
It leaves our network, and it hits the cloud.
It goes from the cloud and it hits their network.
It leaves their network.
It hits the cloud.
It goes from the cloud and hits our in our.
So basically the cloud is just this ugly, nasty mess that somehow all of the traffic it's routed through right.
Some of the routers are secure, and you should be able to trust them.
Many of the raptors and pieces of networking equipment are insecure and again, that's one thing to be thinking about the client.
Basically, with this, you have no idea of the trust of the what you're sending your traffic through, you know, Is it trustable?
Is it not trustable on?
That's why you have things like encryption.
That's one of the reasons why you use things like V P.
M.
So when we're talking about the Internet and we're talking about the cloud, all we mean is that basically the idea with the cloud is you don't know you get you're just going to go to the cloud.
It's somewhere.
It's up there, you know.
It works, you know, it works, you know, it's doing what it's supposed to dio, but really, you have no idea what the traffic would be.
And so really, we start talking about cloud computing.
Now all we're doing is we're simply stating that we just simply don't know where our servers are.
So back here when we didn't know what the traffic is, how the traffic was being moved, we didn't know where the routers are.
Now we have servers, and all we know is the servers are up in the cloud again.
So if you're using digital ocean, let's say you know you're here and you're using digital lotion.
All you know is you're gonna hit some I p address 10 1.1.
This is not an extremely credible I p address Pallister say it is.
Um so basically, all you know is you're gonna go to this I p address this I p addresses.
So we're in the cloud, and so you're just gonna try to round to it and then the Internet, well, without you to which ever server has that particular I p address or domain name or something like that?
Basically, the idea now is like when you say it's on the cloud again.
The concept is is it's just there.
You don't really know where it's at.
So that's the base concept of where the idea of the cloud came from.
Now let's take a moment and talk about abstraction, and we will not talk about how bad my handwriting is.
I've been a computer guy for a little while, anyway, so let's talk about the concept of abstraction.
So basically, in the older is if we go back about a decade or so.
We had individual servers and these were physical servers, and literally everything was on that several, so they would have a Z on processor.
They would have ram, they would have storage.
You would then install the OS, and then you would install the service is so things like exchange your SharePoint or I A yes or a pack your things like that, right?
And everything was on this one physical box.
If the CPU fan for this physical box dies, everything dies.
Us dies of service, dies a storage dies.
Everything goes down, the power supply fails.
Everything goes down right.
If somebody hits this served with a brick, everything goes now and so that's obviously there's a problem with it.
If you have a sink more or less.
A single point of failure for the service is that May supply service is for thousands or tens of thousands of users.
That's a bad idea.
And so that's where the concept of abstraction comes out is basically the idea of Hey, you know, Z, you know, the Z on process, or basically what that is, is that's a CPU that's processing.
So those eons processor and the Ram can we turn that into its own thing?
You know, as far a storage is concerned, Can we abstract that out?
Can we make that you know its own thing?
You know, put that somewhere.
And then, as far as the operating system and possibly service is, can we then break that out and make that its own thing?
So that's basically the idea of Hey, can we Can we turn the like the operations of the service's and basically a single file that can be moved around that's literally not physically connected to a server?
Because remember, back in the old back in the old, nasty days, if you were installed a server operating system onto a physical machine, it was duct taped to that physical machine.
You couldn't just move an operating system around willy nilly.
You had to do a full re installation process with a full migration process, and it really sucks.
Nowadays, you can literally just take a VD.
I file copy, paste, toe a different hyper visor, and it could be up and running literally in a couple of minutes.
And so how that's done is we have stranded things out.
And so that's where as far as the processing goes, that's where I was talking about before with the VM, where hyper visor and basically the virtual ization cluster so we can have a rack of servers here they use VM where again, I'm just saying, being where I'm not sponsored by them, it could be Citrix.
That could be one of the many Lennox variations, something like that.
But basically we can have a virtual ization cluster here.
So all of these boxes, they have a hyper visor installed onto them, and they have a processor.
So they have a Z on processor and they have RAM, and they have some of their own internal storage just so that they can actually function right.
And so basically these air now basically a processing cluster.
So the idea being is whatever machine is currently available.
You can move tasks around.
You can move things around as need be.
If a machine of physical machine fails, you can very easily move tasks.
You can move things to other physical machines without it being a big problem.
So basically, you have this bm where or you have this virtual ization cluster and then what you have beyond that, Then, as you asked, where is the story?
So before we had historic again, it was on the physical machine.
And so now we can have something called a sand a storage area network there I metric crap ton of these options, but basically with a sand, then we have another rack that has your stand.
And in that basically, you have what are called storage devices.
So these storage devices, they're only responsibility is to store data.
You don't really run an operating system on these.
You would not.
You would not play Frogger on these devices.
You're not You're not new word processing on these devices.
I mean, yes, their computers.
Yes, technically, they haven't operating system on them, but it's not the kind of operating system you think about it.
The operating system, they have on them is more akin to your DVD player than it is to your your laptop computer.
And so, basically they're only responsibility is to store data and then depending on what your policies are, make sure there's reliability and that there's redundancy.
And so the idea as you have these Veum, where machines you have these VM were hyper visors and they're able to send and receive data from the sand and soas faras.
They're concerned the sand is just one logical unit to them.
So they go to the sand, they say through the sand.
Hey, I need this data.
Sand provides the data again.
Does it come from here?
Who knows?
Does it come from here?
Who knows Doesn't come from here.
Who the hell cares?
You ask the sand for data on the sand gave you down.
You need to write data.
You need to be able to save data.
So again that goes back.
And so you know, you're just give that data to the sand, does it store it here or here or here you literally don't care.
And so the nice part about abstracting the sand abstracting the storage out is again you have the ability to then automate things like fault, tolerance and reliability.
So if the some hyper visor sends data to the sand, what the sand can do is it can actually make copies.
So let's say you send out of the sand as the sand says, Okay, I'm gonna put one copy of that data here, and I'm gonna put one copy of that data here.
And then another hyper visor sends down into the sand and the sand says, Okay, we're gonna put one copy of that here and one copy of that here.
Reason being is, let's say one of the storage devices fails.
Then there's a copy of your data somewhere else within the sand.
The sand is then able to rebuild itself, do replication and all that kind of stuff.
And then again, basically, you don't You don't have to worry about a single hard drive failing.
You don't have to worry about a single story device.
Failing.
All of that is based off of the sand policies you just pushed and pulled out into the sand.
Storage is its world.
Compute is is world.
Well, then we start thinking about the operating system itself again.
That final component down here when that's where it could talk about the the VD eyes.
Basically, the beady eye folder is What's this thing doing?
Basically, the VD I folder are the VD I files.
These are your your operating systems, right?
So these are your virtual operate system.
So what you do is instead of stall installing windows onto a physical machine, you create a virtual machine for Windows Server 2012.
So you create a 2012 VD I for active directory, you carry a 2012 VD I for exchange, you create ah Lenox D A.
C P server, and basically all of those.
Those are all basically entire machines that are now simply files.
And so what can happen then is these are all saved within the sand there, saved within the Sam.
And so for the hyper visors.
If they say okay, we need to load up a particular virtual machine.
Okay, You know, we need the 2012 active directory.
People are logging in for the day.
We need the active directory.
Basically, you can have a hyper visor here, communicate with sand, say, give me the 2012 active directory virtual machine, and then that could be then used by that particular hyper visor.
A different hyper visor can say I need the extreme, sir, but we're doing email service is I need the extreme server and then, you know, for, you know, D A, C p and D.
N s.
Basically these hyper visors air that able to request those virtual machines from the sand but in the sand simply provides it.
And the nice part here, then, is what you have to understand is essentially, it's like the data the data is in.
The sand of virtual machine is in the sand.
But the process is happening over here, you know, within this virtualization cluster.
So the nice part is, let's say you're active Directory system is running on this particular server.
So this particular server is Iranian active directory.
And then what happens if a CPU fan fails?
What happens if a process or, you know, power supply, whatever fails so this completely dies the cluster here, the management of the cluster realizes, Oh, crap, this physical machine died.
So now we're going to ask this machine down here to request the active directory virtual machine.
And so, basically, since it's simply requesting from the sand, it can be moved more or less within milliseconds.
And then basically, that active directory server can now be up and running again, even though the machine that it had previously been on has literally physically died.
And so this is one of those concepts with abstraction is the idea is how How do you look at that old physical server?
That old physical server, the CPU, the ram, the storage, the operating system, the service is everything was super glue.
If anything failed, everything failed.
So how can we abstract out those different service is how can we have tracked out the process?
And how can you extract out the story?
How can we abstract out the OS?
How can you even abstract out the service's themselves?
How can we make them their own individual thing so that we can interact with them or fluidly and more dynamically, depending upon the situation?
So that's the basic concept of what we're talking about when we're talking about abstraction.
So was that about as clear as month so far?
Don't worry.
As you watch follow on videos I think a lot of this will start to make a lot more sense again.
One of the issues when you start talking about cloud computing, especially with new people, is there's a lot of concepts here.
There's a lot of terminology.
There's a lot of different technology that is very hard to explain this type of thing again.
You don't know the difference between of'em wearing a sand if you don't know what those words actually mean.
Trying to explain some of this stuff could be a little bit difficult, but no worry if you if you want to follow on classes, I think a lot of stuff will start to make more sense now.
One of things I want to talk about.
Now we're talking about cloud computing again, and we talked about abstractions we talked about.
Basically breaking apart all of those different layers is the concept of compute.
So in this modern world, compute is now its own individual, basically service that you can interact with on its own.
Now, when we start talking about compute, there's a lot of different ways to to think about compute in the different technologies that allow you to offer compute more or less of the service eso There's a standard virtualization technology, so if you talk about things like virtual machines or things such as containers, so containers are a type of virtual ization.
Basically, what this is is where you're able to take an entire operating system with whatever service's are installed on that operating system, and turn that into a fine and basically wants is a file.
Once it's a VD I file, they can then be moved around and interacted with, just like any other file or folder on your system.
So just like right now you have pictures or you have MP three or you have video files and you can simply copy and paste them.
Or you can email them do things like that.
Basically, that's what you can do with an entire, uh, virtual operating system.
That entire operating system is simply in a file, and then you can simply copy and paste it onto a machine that has something called a hyper visor.
And then that machine is able to then run that server or possibly multiple servers.
So if you're using something like VM wear or hyper V, you can literally have 10 or 20 virtual servers, virtual machines running on one physical box.
That physical box then splits up the processing amongst all of those different virtual machines that are running.
Depending on what requirements you've set up again, you can have a cluster of virtual machines that communicate back with a sand in that sand.
That storage area network.
You have the virtual machine files, and then those hyper vier advisors can then request those files and move them around again as they've been configured to do so.
If you have a physical machine that fails, then basically simply another hyper visor within that cluster can request the virtual machine.
Find a file, and then that virtual machine could be up and running in no time flat, or if one physical server is being overloaded.
For some reason, there are so many requests for the virtual machines that are running on that physical box that is Peggy.
Now the CPU is going above 80% consistently.
Then again, basically in that hyper the hyper visor cluster, that virtualization cluster, basically a virtual machine, can simply be moved to a different physical machine so that there's less load on the first machine, and then the other machine can work appropriately.
And so this is the kind of thing to be thinking about again.
This whole idea of where compute compute is now a service.
And when you started thinking about compute being a service, you then get into what's happening now.
Something called a server.
Less architecture, which I find awesome, find awesome.
It is.
So if you don't think serverless architectures or sexy, I don't know how you can call yourself a geek.
Basically, serverless architectures allow you deal is you have, ah, code that is running on your server.
But that code can actually call ah CPU processing from a different server, basically through almost like an A P.
I call.
So let's say you're using PHP scripts or No, do you?
Yes, scripts or something like that, depending on what the service for several its architectural Laos.
And so what you can do is you can say, OK, let's say, er, you need to encode a file so basically again you have a video file, you need to encode it to 10 80 p or something like that.
So normally what would happen is that file would be copied one way or another, Toe and encoding server, that encoding server within half configurations.
And then that encoding server would do all of the encoding, right?
So you would need a server and you need the encoding software on the server.
You, when you do that, could do the configurations.
The whole nine yards, right?
Well, now what's cool about serverless architecture is what you can do is you can simply write a line of code, and you can call basically just a serverless architect.
It is like a a P.
I call right.
You don't even know.
You don't really know if it's a Lennox server or it's a UNIX server.
It's a Windows server.
Anything else?
Basically what you do is there's an I P address.
There's a domain name or whatever else that you point thio and basically you make a call and you make a call to them and you give it the keys and give us some specific information.
And then you say OK, so I'm communicating with this architect.
This serverless architecture, and basically what you say is okay, I've got this file.
I've got this file your architecture of needs to do X, y or Z to the file, and then it needs to output the results over here.
And so what happens is that architecture is built do something such as encoding videos.
So what that architecture does is that our content serverless architecture in codes videos.
However, you tell it to encode videos again, you don't know the operating system that's running on it.
You may not know the encoding suffer.
That's running on it.
All, you know is that it in codes videos.
And so you make a call and then that serverless architecture.
What that does is that that grabs your file.
It does the encoding.
It spits the output off to wherever you wanted to be out put it to you and it's done.
You don't have to worry about system administration on that surveillance architecture.
You, you, for you you don't have to worry about anti virus.
You don't have to worry about maintenance.
Basically, all you have to do is you make a call four or the CPU for the compute.
It does whatever you've asked it to dio it outputs and then it goes away.
And so this is one of those really powerful things again in this modern world of cloud computing, where it turns the old ideas of system administration completely like literally, completely on its head.
When literally you could do things like Call compute, you can call processing the same way you would ask for an image file or be able to download something on the Internet.
So those those those are some of the things to be thinking about.
We started talking about compute in the modern cloud computing environment is the idea of okay that that processing that's happening, that could be its own, a separate little world that could be its own separate thing.
You know, away from that the normal servers and stuff that we normally think about.
Now let's talk about storage so storage again.
So we have compute, so we have compute.
But again, even in the service architecture, take a file from here output to there, which means we need to hear, and we need a there we need we need some kind of storage for our cloud computing infrastructure.
Now, when we start talking about story in a cloud computing infrastructure and maybe a number of different things now, the one thing that you may be using, especially if you're using your own private network.
You you own your own equipment is something called a sand, a storage area network.
What a storage area network is is essentially more or less.
It's, Ah, it's computers with their own.
They're only task is to store data.
And so what you could do is you can create a cluster of these storage devices and then based off of the configurations.
Then what will happen is files will be moved around automatically within this cluster on the sand, as need be so again, depending on what what redundancy you want, what reliability you want.
You may copy a file two times, maybe maybe files on two different storage devices.
Or, if you've got a lot, lot of money, you may copy a file four times, so it's on four different devices.
So if you have 10 storage devices in your sand and let's say four of them get destroyed somehow, if you make four copies than most likely, you're going to be fine.
So that's one of things be thinking about when you're thinking about storage area networks and building us out is one thing to think about is again.
What?
What is your risk tolerance?
Do you simply want to make sure that if one storage devices destroyed, you'll be OK or again?
You know what happens if a tornado comes through and literally destroyed, like physically destroys half your rack?
If that happens, based on ho, how you build up your storage area network, you may or may not still be able to have all your data when the cool parts to historic area networks is.
Once you start dealing with a storage area network, you can then put those storage devices in different places, right, So you could have ah, part of your your sand basically being in your internal network.
So in your soul server room, and then it can communicate with other devices that are maybe at a co location facility.
So if you're worried about oh, you know what happens if a tornado comes through or a flood, a flood comes through and destroys my entire server room.
If you know all the data is in real time being replicated office, some other co location facility, then you know.
Then at least if nothing else, all of your data is not going to be destroyed.
So by abstracting out the concept of storage, you can do start doing some fancy things with that story today.
You can't d'oh when basically you've got a hard drive on a server again if you go back about 10 years and you talk about storage for servers, basically what he had more or less what you had is he had a hard drive on the server and then hopefully you had a backup regime that worked.
Hopefully that was that right?
So your hard drive physically died, then you then you basically pulled from the backup and hopefully everything's running.
Then you had things like raid.
So we're done an array of inexpensive discs.
That's where you could tie multiple hard drives into one.
A logical hard drive for the server on DSO, with the idea being if one of the hard drives failed, then you still have access to all of your data, and you could simply replace the one Dr.
But again, there was a problem there, and I saw this in the real world.
It's what happens if a single raid card fails what happens of multiple hard drive actually had that I had multiple hard rise fail in a raid.
Five ones like one failed.
And then literally, while I was writing down the information so I could replace the one that had failed, another one failed and their server died, right?
So that was a thing.
So back then, not that long ago.
All the story was with that physical box.
So if there was a failure of the raid controller, there's a failure of multiple hard drives, right?
You were screwed.
Basically, all you had was your backup.
However long it took you to be about restoring our backup the nice part.
Now, when you start talking about storage area networks is again an entire store and server.
An entire storage device can literally just be stole.
It can just go the hell away, just gone.
And as long as you've configured your sand, probably your users are gonna notice.
You see, you know my notice, like it scream that But the nice part is you'll be getting screamed at, but the user's won't know there's a problem.
I always prefer getting screamed at by CEOs.
I don't know what it iss getting screamed at by a CEO is so much easier to deal with thinking script in debt by the users.
But that's a right.
So so even if an entire storage device disappears or is destroyed, the access to to whatever data is on that sand will still be available to the user's again, depending on what replication strategies and you have going on.
All the data could be offered a cold location facility so that even if your entire office is destroyed, that data is there.
Depending on what architecture built out, it may be accessible to you.
We start thinking about stored, and we start abstracting out the storage.
You can also then simply go to providers such as a dump US or azure for stored service's.
So if you go to eight of us, any of us has multiple storage service is now.
I actually like using eight of US Glacier.
That's a very inexpensive but slow storage solution.
But if you go to Amazon, you'll notice that they have a lot of different storage options for you, so you can use glacier.
You can use a stored block storage.
They have a lot of different storage, and so for your servers or for whatever you're doing.
You can point your servers at whatever storage service you think is most appropriate in The nice part is is, Then you can decide what storage is appropriate for your price point and for your requirements.
So for me, I actually use eight of us Glacier.
So eight of us Glacier is a storage solution that is very inexpensive.
It's something like 11 cent per gig for story.
Well, the reason is this is not real time.
Access is not real time access.
You pump data up to eight of US Black Glacier.
It stores it for your real time.
But if you actually want to be able to recover the NATO for some reason, basically, you actually have to put a request in into that request.
We will grab all the data you want, put it into a format that you can actually download, and then you will have to download and so that can actually take up to a couple of last time I did It took a couple hours.
Maybe it's a little faster now, but the idea is it's not.
It's not really time access story, so I use it as a backup solution.
So again, as far as backup and data goes, I have 1000 different backups for all my files.
So there's a backup here.
There's a back up here and there's a backup here.
But again, one of the questions has to be is.
You know what if a tornado comes through?
What if a flood comes?
What my house burns down, right?
Well, then what's happened?
Your data.
So I'm backing up to eight of us Glacier.
It has a very low price point because again, it's a very slow recovery process of you actually need to get it.
And so I have that as my fault.
Tolerance.
So I pay, like, 20 bucks a month for quite a bit of storage up there.
Uh, just in case something happens.
And so that's one of things that you can look at as you could go to AWS.
You can go toe azure depending on what kind of story you didn't do.
You need really fast accessible storage.
You can go there, and you can simply pay for however much you need.
If you need to slow but keeps toward, you can pay for However, much you need.
And so that's one of things to be thinking about again in this modern world of cloud computing is when you abstract out, you can have a local sand, or possibly you could be using AWS or is your storage.
You can use these different things, and you can figure out what price point and what requirements you have and pick the product that works for you.
So those are some of the things to be thinking about with storage and cloud computing.
So now we need to talk a little bit about databases when it comes to cloud computing.
So I'm gonna tell you a little secret.
I'm not sure with secret, if that's what I'm supposed to say, though.
But the reality is there's so much of what we deal with in the I T World anymore, really is databases, and it's simply pushing and pulling data out of databases.
Right?
People create these fancy cool, wacky front ends, and it looks super sexy, and it looks super high tech.
But really, most of what the powerful thing that's happening is just simple.
You know, sequel queries or whatever sweet sequel statements going back to a database somewhere, and then it goes to the database that either requests information or puts information, and and then, you know, they tried to try to splash it up with graphics to make it look a lot cooler than it is.
But if you go Thio sites, you know whether you're going to amazon dot com.
But you're goingto iTunes.
So many of the service is that we use any anymore, basically our database driven.
So what happens is there's data within these databases you can you can do searches.
So again, if you go to amazon dot com and then you're looking for a lawn chairs and unplugging Long cares a certain weary.
And if you see pictures, you see all this fancy stuff.
In reality, all that Web page is doing.
His estate in lawn chairs is then going to a database.
It's running a query based off of what you plugged in a search, and then it's out putting the results.
That's outputting data that in the Web page it takes that data formats a toe look very, very, very pretty.
And so it looks high tech and sophisticated when it's really just again,