Welcome back.

So today's video I want to do an introduction to platform as a service P A s.

So this is a very important concept in the modern world, and this is one of the ways that a lot of code gets deployed for production environments.

Now, one of the big things that confuses a lot of new people.

When we start talking about things like server less architecture, their minds kind of just explode because they say, I don't understand.

How can it be a server list architecture?

If there has to be code somewhere that's running on something.

Doesn't that have to be a server?

And the important thing to understand?

We start talking about things like serverless architectures.

Is that again?

It's kind of like, Yes, there is a server, but you don't really think of it the way you think of old fashioned servers.

So, yes, there is a server that runs the code, but logically, you don't think of it as a server, right?

So back in the old days when we were dealing with servers.

If we're going to be deploying applications right, we would have a physical machine.

We would have the operating system.

We would then have the service or the application installed on the operating system.

And there be all of these configurations.

So if you wanted to be able to maintain that application, not only did you actually maintain the application, the code itself, but you also had to update the operating system.

You had to run antivirus scans.

You had to do backups.

You had to dust out that CPU fan because I know some of the young people out there are, like, Why?

Why does it keep talking about CPU fans?

Because if the fans killed more servers than almost anything else, why why'd the server crash?

See, if you fan like that's just the fact that matter, right.

So back in the old days, if you're going to deploy a new application for either your production environments of your internal users or for the outside world basically again, you'd have that physical machine with the server operating system with the app installed on that, and you would have to maintain all of that.

So when you're maintaining a server, you're maintaining not just the application and the code, but you're you're maintain this software in the operating system and the drivers and the CPU fan and all of that kind of stuff, right?

And that's basically the old way of doing things that worked again 20 years ago.

That was a great way to do stuff that was better than a pen and paper.

But nowadays that's you don't want to be dealing with that kind of thing, right?

If you're cool, you're cool Python code or a ruby on rails coder.

You don't want to get your hands dirty with things like CPU fans.

You just want to be able to deploy your code somewhere and just have that code run.

And the cool thing is, in this modern world, you can have that again.

Basically what a platform as a service is, it is a platform as a service.

The old fashioned platform is a service that most people are used to is basically Web hosting, right, So you think about web hosting.

If you're going to deploy a website, right, you're unemployed.

Website.

You're not gonna be a bill.

A physical machine.

You're most likely not even going to spin up a virtual instance of an operating system.

What are you going to do?

You're gonna go to go, Daddy, you're gonna go to host Gator.

I'm gonna go to one of the thigh was in web hosting solutions out there.

You're gonna find one with the particular language is that you need most likely something like PHP with a database that you need something like my sequel and they're gonna upload the code.

You're gonna do some configuration modifications, and then voila.

Your website is running without you having to worry about the server, right?

You're not worried about Cebu fans?

You're not worried about the anti virus they're not worried about any About you're worried about uploading your code, making sure the configuration finals point to the right places on.

Then your code simply runs.

So that's what we're talking about.

At four.

Platform is a service.

So this is important nowadays again, things that you'd be thinking about things like web applications.

Right?

So if you're gonna be building a web application, whether internally for your company or for your external users, right, you need to be thinking about Where are you going to host that application again?

Do you really want to worry about the physical server and all the things that go along with it?

Or do you simply want to go to a provider that gives all of that to you for a reasonable cost?

And then you can just deploy it and not worry about it anymore?

Or things to be thinking about is more complicated Web applications again?

You start thinking about this whole serverless architectures, that type of thing, where you're going to have code that's going toe to do stuff to other things, right?

Basically, that code has to reside somewhere so that it can communicate with a W S O that can communicate with azure so that it can communicate with these cloud based service is right.

Eso One of things you could be thinking about is using platform as a service.

You put your code up on that P.

A s, that platform as a service, and then when it's up there, it can run and it can do things for you.

So again, for platform is a service, you could be doing simple database tasks.

So imagine if you wanted Thio run report every day and email it about, Let's say, sales for your company so you may not need a website the way you think of a normal website.

But you do need someplace toe to run that PHP or that python code, right so that code could be sitting up on a platform.

As a service, it can connect to a database.

It could do a sleep that you can do it, what's called a select statement and can select, Let's say, any sales that happened in the past day.

It consort them based off of whatever you want them sorted on, basically, can then point that out to an email and then send that to whoever you want the notification to go to.

So think about that.

All of that is Web based technology.

That's not necessarily a website, right?

You do need a you do need to have python or PHP or ruby to make it run.

It does need to connect to a database.

It doesn't you can connect to an email service, whether simply through the mail function and PHP your ruby or through something like send grid right, so it means all of those cloud Web service is, But there's no website you're going to go to.

It's just automatically going to run in the background.

So that's what we're talking about.

We're talking about Platform is a service, and that's why platforms the service is really important right now.

So now that you know what platform is a service is we need to talk about how you're going to select what platform you're going to use for your service is right.

So the important thing to remember again when we're talking about a lot of these technology concepts is that platform is a service unto itself is just a concept that doesn't really mean a whole hell of a lot.

When you're really going to be looking for is what technologies are being used by vendors in order to give you that platform is a service, right?

So if you're going to be coding in a particular language, supplies supplies, whatever vendor you're going to go, it needs to support that language, right?

So you're gonna be, uh, coding and ruby on rails, and you go to use a platform as a service, you need to make sure of that platform actually supports Ruby on rails.

One of the big issues, I suppose you could say with platforms as a service is you don't get a lot of modifications with the configuration, right?

They give you whatever the hell it is that they offer you, and that's it.

It's not like you can go to go, Daddy.

And after you've set up your hosting account again, if you're basically using just a platform is a service.

So just the platform account.

It's not like you can go in there and start willing.

Nearly adding language is adding interpreters, that type of thing.

They're going to tell you what you can use.

You get a 10 my sequel databases, you get PHP seven.

You get this, you get that, you get the other.

If you need something else, that's nice.

Go find a different vendor.

So one of the important things be thinking about what we talked about.

Platform is a service that is just an overall concept, and then when you look at is the vendors and then are going to be offering a specific technology, so they will specifically say we're going to give it offering you a Lennox server that is running a Paki that has PHP seven.

That gives you 10 my sequel databases that does this does this and does this if that's what you need.

Great.

Go with that.

If not, go somewhere up.

So So we're gonna be looking, taking a look at host Gator.

So one of things that host Gator offers is they offer Ruby on rails were go.

Daddy doesn't.

So if you're going to need Ruby on rails, then you will go with host Gap Coast, Gator versus Go.

Daddy doesn't really matter.

You know how many stars the vendor gets?

Basically, the fireman is does it offer what you actually need?

And then finally, we're going to take a look at Roku that that shows you kind of how you can start using platform as a service for your overall infrastructure.

Again, we start creating a lot of larger projects, not simply things such as websites, but again this larger scale projects where you're going to be doing reports, they're doing notifications you're going to be maintaining database is doing a lot of complicated tests.

Then you could go to service such as Hiroko, which offers you even more things than something like Go Daddy or host Gator will.

And so something to be thinking about is you have to think about what are your requirements again for what you are trying to do?

What are your data requirements for things like security?

Do you have to have PCR requirements?

You have to have a hippo requirements.

You have to have some other privacy requirements, right?

So what, you would look at what the platform as a service is basically, are they compliant with those particular things?

If they are used them, if they're not, find something else again.

Do they use the Cody and languages that you need?

So you go when you take a look.

And if you're using Ruby on rails, you basically you just go down the list.

You're like OK, yes.

They use ruby on rails.

No, they don't use Ruby on rails and go from there again.

If you have a whole bunch of code in ruby on rails, it doesn't matter if they support python because you've got Ruby right on Dhe.

Then you start looking at some of the other features and functionality that they have things like backup, so some of them will do things like real time backups for daily backups.

And so that's something that's really nice.

Is if your platform is a service Simply again, you should be setting up your own backup.

To be clear, to declare.

You should be setting up your own backup and disaster recovery routine yourself.

But if they also offer it as a backup to your backup, that could be a valuable thing, right for some, raising your backup routine crashes, and they're offering something like that just as part of the service that will be good for you.

Other things to be thinking about is, like denial of service attack prevention.

So does their infrastructure prevent denial of service attacks?

Again?

You're dealing with a larger company.

Or let's say you're dealing with a company that may have some political issues nowadays again, politics politics is something you have to be thinking about in the modern world technology.

So if you're dealing with, like a bright bar of the world where you're dealing with, you know any of these political things, you have a you know, some APS for Republicans or some abs for Democrats or some absolute Christians or some APS for Buddhists, or whatever something to be thinking about is, does the service that you're using offer protection for denial of service attacks?

So if somebody tries to attack the infrastructure that you've built on the platform, will that be mitigated?

Will that be prevented?

These are some of things to think about it again.

This isn't, you know, basically all you do, and that's what you do.

In a lot of times in the modern world, technology is you literally you just you just look down the text spec list and you see what they offer.

You're okay.

Well, this one offers this who?

But this offers this.

This one offers this.

Oh, this one doesn't often that Okay, this offers this and this and this.

Oh, but this one offers this this and this.

And then you sit there and take a look in price and take a look at everything else.

And then you decide what's best for your particular situation.

So with that, let's go over the computer.

I'll show you three examples of platforms of service will take a look at Go, Daddy.

Go.

Daddy offers to take a look at what host host Gator offers, and then we'll look take a look at what Hiroko offers again these air simply three examples.

Like a lot of things I talk about.

There are a zillion examples out there.

I'm just picking these because they are representative of what you will find.

And so when you're going out in the real world, do a lot of your own research and figure out what works best for your particular situation.

So first platform that we're gonna be taking a look at is Go, Daddy.

And we're gonna simply be looking at their Web hosting plants.

Now.

I know some people maybe like what?

What is this?

Allies just showing us Web hosting plans.