+91 0562 355 3068 info@technoturfitservices.com

SERVERLESS COMPUTING

source, code, software

INTRODUCTION

Hey you guys! yes you are reading correctly “SERVERLESS COMPUTING” in this blog post we are going talking about it. Well, when we  think about serverless computing it might blows our mind because till now we all have hear very common and useful real world name that is server.

serverless does not means that there is no server involvement but it means that we are not responsible for managing and provisioning of these servers,it's sort of outsourced to the cloud provider whereas we are as a development focused on writing code or business logic

Serverless Computing?

It is a method of providing backend services on an as-used basis. A serverless provider allows users to write and deploy code without the hassle of worrying about the underlying infrastructure. A company that gets backend services from a serverless vendor is charged based on their computation and do not have to reserve and pay for a fixed amount of bandwidth or number of servers, as the service is auto-scaling. Note that despite the name serverless, physical servers are still used but developers do not need to be aware of them.

Benifits of Serverless Computing?

Improved utilization — The typical cloud business model, which AWS championed early on, involves leasing either machines — virtual machines (VMs) or bare-metal servers — or containers (such as Docker or OCI containers) that are reasonably self-contained entities. Virtually speaking, since they all have network addresses, they may as well be servers. The customer pays for the length of time these servers exist, in addition to the resources they consume. 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.”