Introduction To Serverless
Computing
By Tharuka Vishwajith
Any developer focused product which abstract
out the underline servers = Serverless
Characteristics of serverless
• No management of server hosting
• Self-auto-scale and auto provision based on load
• Cost based on precise usage
• Performance capabilities defined in terms other than host size/count
• Implicit high availability
What includes?
• Function as a service – FAAS
• Database as a service – BAAS
• Storage
• Messaging
• And more…
Key benefits of serverless
• Handling servers by a small team with the software product is very difficult.
• Spending more time on building software and less time on administration
• Pay as you use
• Provide abstraction for the developers
Abstraction make more productive
Machine code -> Assembly code -> Application code
Function as a Service (FaaS)
Overview for FaaS
• No host configuration
• Pay for what’s running
• Scale up for the demand
• Automatic spin down
You have your Pease of code and you can put it into FAAS (Function as a Service)
Can easily connect theses services with small custom code
Language support
If you want in on premise then use
https://www.openfaas.com/
FaaS use cases
Good for
• Schedule tasks
• Trigger batch procession
• Email someone
• Thumbnail Procession
Not good for
• Long running jobs
• Stateful back end Ex: Actor based system
• Fine grained scaling controls

Introduction to serverless computing

  • 1.
  • 2.
    Any developer focusedproduct which abstract out the underline servers = Serverless
  • 3.
    Characteristics of serverless •No management of server hosting • Self-auto-scale and auto provision based on load • Cost based on precise usage • Performance capabilities defined in terms other than host size/count • Implicit high availability
  • 4.
    What includes? • Functionas a service – FAAS • Database as a service – BAAS • Storage • Messaging • And more…
  • 5.
    Key benefits ofserverless • Handling servers by a small team with the software product is very difficult. • Spending more time on building software and less time on administration • Pay as you use • Provide abstraction for the developers Abstraction make more productive Machine code -> Assembly code -> Application code
  • 6.
    Function as aService (FaaS)
  • 7.
    Overview for FaaS •No host configuration • Pay for what’s running • Scale up for the demand • Automatic spin down You have your Pease of code and you can put it into FAAS (Function as a Service)
  • 8.
    Can easily connecttheses services with small custom code
  • 9.
  • 10.
    If you wantin on premise then use https://www.openfaas.com/
  • 11.
    FaaS use cases Goodfor • Schedule tasks • Trigger batch procession • Email someone • Thumbnail Procession Not good for • Long running jobs • Stateful back end Ex: Actor based system • Fine grained scaling controls