In this presentation we will discuss the evolution of IaaS, PaaS, CaaS, FaaS and how serverless computing is beneficial and what are the challenges we have faced so far

1. - OmVikramThapa

2. EVOLUTION

3. SERVERLESS
EVOLUTION

4. CLOUD
PROVIDERS

5. WHY
SERVERLESS?

6. SERVERLESS
JAVASCRIPT

7. SERVICE
WORKERS

8. AWS
LAMBDA

9. AWS
LAMBDA
BUSINESS
MODEL
With the Lambda model, what the customer leases is
instead a function -- a unit of code that performs a
job and yields a result, usually on behalf of some
other code (which may be a typical VM or container,
or conceivably a web application). The customer
leases that code only for the length of time in which
it's "alive" -- just for the small slices of time in which
it's operating.
AWS charges based on the size of the memory space
reserved for the function, for the amount of time that
space is active, which it calls "gigabyte-seconds."

10. BENEFITS

11. BENEFITS
Lower costs - Serverless computing is generally very
cost-effective, as traditional cloud providers of backend services
(server allocation) often result in the user paying for unused
space or idle CPU time.
Simplified scalability - Developers using serverless
architecture don’t have to worry about policies to scale up their
code. The serverless vendor handles all of the scaling on
demand.
Simplified backend code - With FaaS, developers can create
simple functions that independently perform a single purpose,
like making an API call.
Quicker turnaround - Serverless architecture can significantly
cut time to market. Instead of needing a complicated deploy
process to roll out bug fixes and new features, developers can
add and modify code on a piecemeal basis.

12. CHALLENGES
⚫ Testing and Debugging become more challenging
⚫ Serverless computing introduces security concerns
⚫ Serverless Architectures are not build for long
running processes
⚫ Performance may be affected
⚫ Vendor lock-in is a risk
⚫ Alerting & Monitoring is problem
⚫ Versioning & Rollback is tricky

13. CHALLENGES
(COLD START)
Serverless computing continues to evolve as serverless providers
come up with solutions to overcome some of its drawbacks. One of
these drawbacks is cold starts.
Typically when a particular serverless function has not been called in a
while, the provider shuts down the function to save energy and avoid
over-provisioning. The next time a user runs an application that calls
that function, the serverless provider will have to spin it up fresh and
start hosting that function again. This startup time adds significant
latency, which is known as a cold start.
Once the function is up and running it will be served much more
rapidly on subsequent requests (warm starts), but if the function is not
requested again for a while, the function will once again go dormant.
This means the next user to request that function will experience a
cold start. Up until fairly recently, cold starts were considered a
necessary trade-off of using serverless functions.

14. REFERENCES
https://aws.amazon.com/serverless/
https://stackify.com/function-as-a-service-serverless-architecture/
https://www.zdnet.com/article/what-serverless-computing-really-means-an
d-everything-else-you-need-to-know/
https://www.cloudflare.com/learning/serverless/why-use-serverless/
https://docs.aws.amazon.com/lambda/latest/dg/lambda-python.html
https://docs.aws.amazon.com/lambda/latest/dg/lambda-java.html
https://docs.aws.amazon.com/lambda/latest/dg/lambda-nodejs.html

15. THANKYOU