Is that cost money?

If you appreciate this education, please think about going to Eli the computer guy dot com and offering a one time or monthly recurring donation.

Welcome back.

So today's video I want to talk about serve Earless architectures.

We've talked about client server architecture.

We talk about service oriented architecture.

Now we're gonna talk about when the cool newest XY technologies out there several its architecture.

And this is actually something rather new and rather sexy, and definitely something that you should be taking a look into.

So for a lot of new people out there, when they're getting into the technology field, they think some things are new when in fact, they're old.

You get a lot of new jobs out there going virtual servers.

That's so amazing for the old timers were like, Yeah, that was cool.

12 years ago, 12 years ago, virtualization was amazing.

Now we've kind of moved on.

We've kind of moved on.

And so what we moved on to now is what is called serve Earless architecture, basically event driven.

Compute.

So this is really pretty cool in the modern world.

So for Ah, lot of the resource is that are required in order to build infrastructure.

Those have been, uh, you know, sorted out or whatever put out onto the cloud created as basically service is on demand a while ago.

So if you're thinking about things like storage, So if you need storage on the cloud, Uh, that has been something that's been there for a long time.

If you're thinking about networking, if you think about love, the other resource is required in order to build infrastructure.

Those are things that have been available on the cloud basically on and as an on demand service for a while.

But one of the things that has not been there has been compute, right?

So if you actually need to do something with your data, that is normally when you had to spend up at the very least, a virtual server in order to be able to do something, so doing like a video encoding doing any kind of processing, that type of thing you required a server.

And so again we start talking about a server.

When you're dealing with the server, Not only are you dealing with the application that is doing whatever it's doing.

So let's say we're talking about encoding videos.

So not only do you have to deal with FF MPEG, but you also have to deal with the server operating system.

You also have to do with the hardware or the work your lies environment that it's in.

So for me to be able to encode videos in the past, I not only had to worry about the video encoder and all the settings and configurations for the video encoder, but I had to make sure it's her that the operating system was stable.

It was up to date, it was maintained, and I had make sure the hardware and everything else or the virtual environment was where we should be so simply to get a video encoded.

I also had to be a Lennox administrator.

I also had to be able to understanding the virtual ization or or server hardware.

And so all of those things were required in orderto encoded video.

Well again, we're in the modern world where in the modern world we want to focus on what we want to focus on right.

What if we're going to be doing something like an encoding video.

Really?

All we want to d'oh!

All we want to do in life is in code that video.

We don't care about the operating system.

We don't care about the hardware.

We care about the price.

We care about the performance.

We care about the quality.

Those are the things that we care about.

What underlying operating system does it?

I don't care if it's Windows or Mac or Lennox or units or a frickin potato.

If you can encode my video using a potato.

Hey, that's fine by me.

Just tell me what what the access keys are.

Access that potato and that'll be a Okay, so that's what we're started dealing with when we start dealing with a serverless.

Architecture is basically what we're able to do is we are able to call Compute.

So what we're doing is work hauling, compute were telling that compute what what we need to have done.

Basically, we're setting up a configuration for what?

What that compute needs to dio and then that compute does it.

So again, let's stop talking about something like video encoding.

So if you're gonna be doing something like video encoding before you had a certain physical server, then you have a server operating system.

Then you had the encoder on top of that, and then you had to create the system for how to actually get the videos encoded.

Now, basically, what you could do is, let's say you set up a piece of software and what that software does Isa soon is a video file gets uploaded into a folder.

Basically, the file gets uploaded into a folder that's an event that occurs.

So that event then triggers a script to run.

That script calls a server list architecture so basically and encoding service architecture and says, Hey, I have a video file sitting in this for this need that this video file needs to be encoded to 10 80 p 30 frames per second.

All of this other stuff and the output needs to be put in this other folder.

And so what that compute can do is that compute could basically grab grab the video file.

It can then do the processing for you could do the encoding for you, and it could dump it out in the target file.

And that's it.

You're not worried about the operating system.

You're not worried about the antivirus.

You're not worried about the backup or any of that horse crap.

Basically, all you're doing is you're calling the Compute in order to perform a task that compute.

Is that giving you the output?

You then take that output and do whatever the hell it is that you need to do with it.

So that's what we're talking about with serverless architectures.

And that's what makes surveillance architectures really, really, really cool.

So something to think about with serverless architecture, if you're gonna be administering and maintaining service architecture is that the skills that are going to be required for what you do are going to be different than what we're required before.

So again, for me starting an I t like the system administration stuff about 20 years ago, back then, all I had to know was Windows NT four point.

Oh, right, My new windows NT four point.

Oh, basically the Microsoft Siri's of operating systems.

That was good.

That was it.

I didn't have to know scripting back then, and I didn't have to know any programming languages back then.

I didn't have to know Lennox and I have to know, Mac Os.

I don't have to know anything else, right?

As long.

As long as I could, I could figure out users and groups and permissions or whatever.

On a window server, that was good.

But as time goes by, things change.

And so your skill set to use to evolve.

So now we've come to this period of time.

And now if you're gonna be a systems administrator, you have to know, Lennox, you really should know Mac operating system.

You really need to know how to do scripting.

You need to know how to be a big use the command line.

You need to have all of these skills that you simply just did not need before.

Well, as we start going into the future, you're going to need to eat, need to have an even larger skill set and start working Maur on being able to actually do programming.

So we're getting into a world of what is called programming administration.

So back in the old days, right?

If you're going to administer a server, you're going to minister your systems, right?

You double click you left.

Look, you're right.

Click.

Whatever you set up the configurations.

Now, the way that you maintain and manager systems is basically through scripts and through configuration file.

So now simply maintaining your infrastructure looks a hell of a lot more like normal programming than it does again when I was doing 15 or 20 years ago.

And so when we start talking about serverless architecture, one of the concepts, you're one of the words you're gonna be hearing.

It's only called cloud functions.

You may hear cloud functions May.

Here is your functions.

You mean Lambda functions or whatever, right?

The important thing is that whole little function.

So if you know anything about programming, basically what a function is a function is kind of sort of like a mini program within your your program.

So if you need to add something or if you need a random number, let's say you need a random number and your program for whatever you're doing.

You might use random, you know, parentheses, zero comma, 100 close parentheses, semicolon.

So what that would Dio is calling the random function, and it's saying the start number is zero the end numbers 100.

So basically give me a random number between 0 to 100 rights and that that's a function or the male function in PHP.

So if you're if you're gonna be Cindy, e mails out using PHP.

He simply used mail open parentheses that you give it.

You give it the email address or sending to give the subject line, you get the message, you close parentheses and then basically it takes that information, and then it actually sends out the email based off of that.

So you have an email functionality called the male Function.

So when you start dealing with cloud functions, Maur less, more or less is the same concept for your code.

The only difference here is that you're doing more sophisticated things, such as encoding video files or using machine vision or using some kind of writing recognition or something like that.

So, basically like in the past, if you were going to send an email with PHP, you new mail, you know, open, open parentheses and then again, you know who to subject.

Whatever.

Now, let's say ever going to encode a video file, you do like in code video, open parentheses again.

What video file It is where it's going a couple of configurations, and then basically, what that's able to do is that's able to call the serverless architectures.

They will call that cloud compute function, and in that that service will take over and it will do whatever you've told it to.

D'oh!

So this is an important thing to be thinking about again with his modern world of IittIe administration, where Maura and Maur things really are coming down to being able to code in right configuration files.

Less and less is about right clicking and left clicking and that type of thing.

When you start looking at what programming language language is, you'll need to learn.

That's when the issues that you'll run into is different.

Different functions basically different.

Different vendors require different languages in order to be able to communicate with their serverless architectures.

That's an important thing.

Like a lot of people, a lot of people come with me, right?

They say.

Ella Eli, What is the best programming language, or what programming language do I need to know?

And again it's becoming more and more important, toe, look at what you're trying to accomplish and then figuring out figure out what language does that.

So again, if you're gonna be using a serverless architecture, there are certain languages that will work with the different vendors.

So it may be Java and maybe Java script and maybe something called Curl, and maybe it maybe c sharp it Maybe any of these different languages different different components in a serverless architecture might require different languages also.

So a vision, a machine of vision, cloud function may require a different language to communicate with it than some kind of other cloud function.

And so one of things that you're gonna have to be looking at whenever you're gonna be thinking about what programming language to learn is basically what you do is you look at the cloud functions, you look at your requirements and then you figure out which one of these language languages will work best for what you're trying to accomplish and being able to bring in all of his different cloud functions that you may be trying to use an access, so that's gonna be one of important things and think that's gonna make it a little bit complicated for a lot of old school administrators that are trying to get in to this new serverless architectural world is because in a lot of ways, this is really, really, really different than the way that they've been doing.

That's right.

People are, you know, old school I t administrators there usedto I P addresses and default gateways and permissions and security and that type of stuff.

That's how they've thought about administering systems they haven't thought basically right, Right now, these nasty 1000 long script, the 1000 line long scripts where you have connections to all these different service is your inputs.

You have outputs.

You have all that kind of stuff again.

It's like the end result may look a lot the same, But how you actually build the infrastructure is a hell of a lot different.

So these are some of the things you need to be thinking about with the serverless architecture, if you're going to be going in that round.

So with that, let's go over to the computer so I can show you some of the different vendors that offer their own serverless architectures.

And then we'll dig a little bit into the azure serverless architecture and take a look at what's required for image recognition.

Using one of their cloud functions because I think if you start to look at this a little bit better, you'll start to understand how this stuff works and how you need to be thinking about service serverless architecture and cloud functions for how you're gonna be bringing this into your infrastructure.

So the important thing to remember when we were talking about serverless architecture again this is an idea.

This is a methodology.

And then there are many different companies out there creating specific products to accomplish what we're trying to accomplish.

S so I just brought up Google, IBM, AWS and Azure just so you can see that there are different companies out there doing this.

And so it's important for you if you're going to start thinking about building now to surveil its architecture, you look at all the company's beforehand.

You look at all the products they offer, you look at all the requirements, and then you figure out who you're gonna build your applications and your infrastructure off on, eh?

So basically we have Google Cloud and so Google Cloud calls calls their service architecture cloud functions again.