Salas is not just lambda.
All right guys and girls will come to this lecture I just wanted to bust a misconception that sometimes
people develop.
Sometimes people think that lambda is the only thing in several lists which is not true.
There are many many several services in it unless so in this quick video.
Let's take a look at what makes us have several lists and then we are going to take a look at the several
lists ecosystem in Annapolis.
All right let's get into it OK.
Let's look at the properties that makes us Harvey's several US.
Number one no servers to provision are manage either physical or virtual.
Number two automatically scales with usage.
You do not need to set up auto scaling separately.
Number three never pay for idle.
If you are not using it you are not paying for it.
Last but not the least availability and fault tolerance built in.
If an NWS service fulfills this four requirements that means that services suffer less.
All right.
Less pressure test.
Some of the services.
Let's look at Amazon.
Rescuers are simple queue service.
It is a fully managed message queuing service that enables you to decouple and scale micro services
distribute your systems and server less applications for rescuers.
You don't need to set up any servers so rule number one satisfied Eskew is automatically skills with
the usage edge and you only pay when you send some messages through Eskew.
So you never pay for idle and it is inherently highly available so you'd not have to set up multi lazy
manually.
So my caution to you is is obscure sovereign less.
Yes it is.
Now let's look at another service Amazon kindness is data stream.
Amazon kindnesses makes it easy to collect process and analyze real time streaming data so you can get
timely insights and react quickly to new information.
Do you have to provision servers for Amazon kindnesses.
Nope.
So rule number one stands.
Does it automatically scales with the usage.
Now you have to define the shards based on your traffic volume and on that note you also have to pay
for those shards even if no messages are going through it.
However every liability and fault tolerance is built in.
OK so Amazon kindnesses does not satisfy all the four rules of Sara.
Less so is the server less.
Nope not several less.
Finally let's take a look at Amazon.
Easy too easy to is a virtual machine itself.
So you have to provision and manage the server to make it scale.
You have to set up auto scaling grew up on top of it.
And if they easy to his running you have to pay for it.
Doesn't matter if the utilization is zero and to make it highly available and fault tolerant you have
to set up auto scaling up and load balancer.
So Amazon AC do is not several US.
So now you know what makes a service Havre less.
So let's take a look at some of the different services beyond lambda which are several less so for compute.
Of course we have lambda and NWS farmgate for storage.
We have one or several less dynamo D.B. and Amazon S three and four integration and analytics Amazon
API Gateway squares step functions Glu S.A. app sync all of these several less and there are more.
All right so next time you want to know if a service is marvelous or not.
Just run those four rules and if it satisfies then you several less.
All right guys and girls see you in the next lecture by.