Basics of Serverless Computing - BunksAllowed

BunksAllowed is an effort to facilitate Self Learning process through the provision of quality tutorials.

Community

Basics of Serverless Computing

Share This
Nowadays, Serverless computing is another buzzword. It's a new computing model. But it does not mean that the programming logic is running without any server. 

Basically, the users do not have access to the server to manage or configure. They can deploy their code on the server and execute it without worrying about the underlying infrastructure. 

The service providers manage the infrastructure and make the virtual resources ready so that the users can deploy and run their applications at any time.

In the Serverless computing model, users are charged only for resource usage instead of reserving duration as resources are not reserved explicitly. It allows cloud providers to manage containers for functions to serve requests. This eliminates the need for continuously running systems and allows for event-driven computations.
 
Serverless architecture offers immense feasibility for creating scalable applications, allowing code to be written, uploaded, and run without worrying about infrastructure, setup, or environment maintenance. This accelerates development speed and allows for the creation of fully functional and scalable applications in half the time it takes to build them from the ground up.

The major advantages of the Serverless computing mode

  1. Cost-effectiveness: Renting cloud resources is not needed; thus the user has to pay only for the duration in which the program is executed.
  2. Elasticity and scalability: The developers do not need to spend time for setting up and tuning auto-scaling policies. Those are managed by service providers.

The major disadvantages of the Serverless computing model

  1. Performance: The performance of the application or execution time is more compared to running them on dedicated servers. Service providers impose resource access limits, which may affect the performance of an application.
  2. Monitoring: Sometimes constant monitoring cannot be performed by digging into the code and run-time environment.

Examples: AWS Lambda, Azure Functions, GCP Cloud Functions, etc.


Happy Exploring!

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.