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 S O A or service oriented architecture.

So this is a way of designing your I T infrastructure.

Where you focus primarily on the service is that are required and not really this servers themselves.

So when we talk about client server architectural, we talk about something like an extreme server providing email service is or a routing remote access server providing VPN servers.

One of the issues as an administrator is not only are you responsible for the configurations and the connections in order to connect to those service is, but you're also responsible for dealing with the operating system, dealing with patches, dealing with anti virus dealing with all of those things.

So basically, when you're looking at administering your infrastructure, not only are you do you have to deal with the service is that are actually needed by your users, but you're worried about all of the underlying components that actually provide those service is so we start looking at a service oriented architecture.

What becomes very interesting here.

Is this a different way of looking at your architecture?

Basically, the idea being If What if?

What if the server or whatever is providing the service simply becomes a black box to you?

You're no longer worried about the operating system updates.

They're no longer worried about the anti virus or any of those other things required to maintain the server.

All you're really worried about is the connection between the client applications or the users, and the service is that they are trying to get to.

And so why this becomes very important is in the modern world when we start looking at cloud computing infrastructure and we start looking at all these service is that are available from cloud computing providers.

If you start thinking about things Maur as a service versus as a server, you get to do some interesting things again with your infrastructure.

So if you're simply thinking about something like a database service, like in the old days, so if you're going to have a my sequel database, so you're gonna be running a website with my sequel Back End or something like that in the old days that my sequel database would be on a server, probably Olynyk server, that would have something like my sequel, Insult.

And so you is the administrator.

You be responsible for my secret database and you'll be responsible for the mice equal running on Olynyk server.

And you'd be responsible for the Lenox operating system itself.

And you're responsible for all the hardware that provides everything for you.

And so that could be That could be a little difficult.

That requires a lot of time and energy.

And so one of things you could be thinking I was like, Well, do I really want my sequel server?

Right?

That sounds a little weird here, but do I really want my sequel server, or do I simply want some kind of database service?

My software has to connect to a database.

Do I really care whether or not if I own that particular server, or how that particular server actually runs?

So something some of the interesting things you can do with servers oriented architecture is if you build things out, you can start with your own.

My sequel server so you can have my single database and my sequel server.

And you can have all that up and running and you're responsible for everything.

And then you start thinking about it like, you know what?

You know I don't really wanna I don't really want to run my own sequel my own my sequel server.

Because if the CPU fan fails or something like that, everything goes down.

So then you can start thinking about Well, okay, I need these service.

I need a service that provides a my sequel data vice connection and so that you can go to a company.

I'll show you this in a little bit, such as Digital ocean.

And they actually have database as a service service is so you can actually migrate your data to them.

And they actually run my sequel in their cloud so that you now get all of them.

My sequel database service, is that you need, but you're no longer happy.

Never on your server.

But then again, if you're sitting there anything about the service oriented architecture, right?

Is it even okay?

We don't really need the physical server.

I don't really want to worry about the operating system.

Here's an interesting question.

Here's the interesting question.

Do you really actually care if it's even my sequel?

They may be sitting there thinking like, Well, wait a minute.

Well, if I need a I need, um, my sequel database in order to run my WordPress or whatever else.

Of course, I need my sequel.

Well, no, actually, you really don't.

You just need something compatible with my sequel.

You need something that understands my sequel, sequel statements, um, structure, query, language statements and can do something with that.

And so that's where you can go to something like eight of us.

Aurora.

So that becomes very interesting.

So a.

W S.

Aurora doesn't actually run my sequel.

So it's a database as a service that is compatible with my sequel.

But it's not actually my sequel, and with that, you get some very interesting things that you could D'oh!

You can have databases all the way up the 64 terabytes and size, and you can do a lot of new interesting things with it because basically what Amazon has done is, they said Okay, we know that we have clients that use software that requires.

My sequel is a back end.

The problem is, my sequel as it is, has issues just like everything does.

And so they said, Hey, what if we redesign the entire back?

And what if we re just redesigned how our database itself actually functions?

But we allow applications that require my sequel to be able to communicate with that database in the standard way that my sequel is able to communicate?

And so this is a way you are now getting the database service that is compatible with my sequel but is not even actually my sequel anymore.

So this is where we get to with service oriented architecture again.

When you start looking at E mail, service is for your company.

Do you really want in exchange server, right.

So if you have an exchange server with your company, that means you have the extreme server software installed on your server, which means you have to deal with the Windows operating system on your server, plus a deal.

You have to have a physical machine, so we start thinking about a service oriented architecture versus a server.

You started thinking Well, really, I just need e mail service is.

I don't really care if its extensive.

I don't really want to dio with Windows.

There will be frank with you.

So what provider or what other way could I get?

The e mail service is for my end users without being hyper focused on what the actual product is, something like exchange.

And so this becomes important.

The modern world, as we go forward is what we can do is if we start looking at things like service is instead of the actual products and servers, then we no longer have to be married to these particular vendors, right?

Because that's one of the big issues in the technology world is sometimes cos they're doing great things.

Sometimes vendors are doing amazing things.

They just everything they touch turns to gold is beautiful, the price points good.

That quality is good, everything's great.

But again, with all these companies, they'll keep doing that for, like, 556 years, the way amazing.

And then something happens, they get a new CEO.

Something else do what happens on.

Then they start putting out trash, right?

They start putting out Windows Vista anyways, so that probably run into right and the old client server Architecture is if you're dealing with extreme server.

All right, if your email service is our provided by an exchange server, And so the way you think of email service is as just an exchange server, The problem is, if Microsoft puts out a really crap product, you're most likely gonna have to buy that new crap product.

The reason being is because you're not thinking about email service is your thinking about exchange server?

So one of things you can start thinking about is like, Well, if you start building your infrastructure Maur just off of the service, then if Microsoft does something stupid, then you can transition over to another provider that will then provide you the e mail service is that you want.

So that's one of the cool things now where a lot of people don't realize how flexible things have become over the last decade or so.

But the fact of the matter is, is that you kind of a company that's using something like an exchange server.

They can go from the exchange server, migrate over.

All they need is email service is or calendar service and that type of thing.

They my migrate over to Google Premier APS.

Basically business class APS.

They could go there.

They could be there for five or six or however many years.

If that starts going to hell, that you go over to something like office 3 65 because now they're no longer married to the one particular product.

All you're looking at is I need a particular type of service.

You start to see this with things such as storage.

Storage becomes very important when you're building out cloud computing infrastructure.

And so if you go to Amazon or if you go to Azure, even if you go to digital ocean now, basically, storage has simply become a service.

Right?

So for you, for you as the IittIe administrator, what do you care about with story, Right.

So you have to tow upload backup files or you have to have data stored somewhere for your infrastructure up on the cloud.

What do you really care about?

You care about price point, you require you care about robustness and up time, basically, that you can get to your data when you need to get to your data.

Uh, you're worried about whether your your security policies and that type of stuff will work properly with within whatever infrastructure and you're worried about.

Maybe some things like Hippo, our PC I compliance or that type of thing, right?

Notice when I talk about the things that you're worried about is a 90 administrator.

One of things that you shouldn't be worried about is what operating system is running your story.

Service's things you shouldn't be worried about is what specific hardware is running.

Your storage service is right.

Things you don't want to be worried about is again the maintenance and all the underlying stuff for your store service is.

So if you're sitting in there and before back in the old days when we thought about, like, file basically files they're sharing her file storage, you would have a file server and so that file servers was most likely a del machine or an HP machine, and that most likely had a Windows server operating system on it.

And then you would have your raid and then you would have everything else.

And so that was a very particular product.

Now, if you can start thinking about like, Well, I don't really care if I have a window servant Really care if I have a Lennox server?

I don't really care about this technology server.

I just need a store red that that that deals with these requirements and then you go to digital ocean and then you can go toe the eight of us.

Then you can go toe ashore.

Then you can go to sign ology, and then you can look at Windows Server and then you can look at the new Lenox offerings.

And then, if you're simply looking at it as a service that's being provided, you can and go.

You figure out, you know which one of these options fits your needs at the moment, and then you can go with that option.

And then as things go in the future, since you're not really married to that particular product, then again, five or six or 10 years from now, you can look and go.

Okay, well, this is what we built out before, But now you know, we think the service's will be provided from this different place better.

And so that's the important thing to be thinking about when you're thinking about the service oriented architecture versus the client server architecture, the client server architecture you're not only worried about the service is being provided by the server, but you also had to deal with the software and you also to do with the operate system.

And you also do the hardware anyhow to deal with the antivirus and all of that kind of thing, right?

All of that was your responsibility.

When you when you're dealing with a service oriented architecture, you're just you're hyper focused on the service isn't themselves that are being provided.

And then basically, how you look at it is how those service is provided are more of a black box.

You're worried about the connection.

You're worried about the connection between your users or your system, and the service is you're not so focused on on what the actual a back end of those service is our.

And when you start looking at things that way, there is a lot of new cool options on the table.

So we know as soon as I start talking about like Black box service is Oh, I'm starting to make a lot of people scared like what?

What what, what, what do you mean?

I don't really know how this service is air being an offer to me.

What do you mean?

It's a black box where I don't really know what's going on on the other side.

Eli, Eli.

I don't really trust that.

Well.

The first thing that I'll say for anybody that starts screaming and who have been hollering about black box service is, is the fact of the matter is you most likely don't really know what the hell's going on in your own infrastructure anyway.

It's very interesting when you start talking about cloud computing infrastructure, and people start getting really scared about cloud computing infrastructure.

They have a big blind