Key points are not available for this paper at this time.
Serverless computing has emerged as a new compelling paradigm for the deployment of applications and services. It represents an evolution of cloud programming models, abstractions, and platforms, and is a testament to the maturity and wide adoption of cloud technologies. In this research, we discuss the new concept in cloud computing that allows the services computation that triggers the code execution as a response for certain events. Cloud computing as provisioning more servers on demand are one of the primary issues and traffic of servers or load is not consistent. The Services are moved to the cloud and a great change is observed in all fields. People are more comfortable having their services on the Internet. As E-commerce services have reached exponential growth. The problem associated with this research is that the organization often spends huge chunks of dollars only for server provisioning, and another chunk for its security and management. As compared to serverless, the vendor serves all security and management aspects. Mostly the Online service providers are often stuck with unexpected traffic. Having more provisioned servers creates a hike in prices. There are needed to be a solution where vendors can only have to pay for the services on demand and describes serverless infrastructure, which assists to do all without taking care of these as a simple model and a simple structure. In this research, the serverless architecture service is providing the use of functions, which are on clusters and compels users "Pay as you go", is more refined in serverless, and now is known by "Pay what is used". It represents an evolution of cloud programming models has gained increasing attention by researchers. It concludes the impact, legacy application migration and using this new approach as standard to build the application. Serverless architecture is far greater than having a legacy approach. Its word to mouth to say serverless will prevail all others but still having the approach might take time. This is not only a cost-effective factor; rather a huge portion of service is somehow is outsource to a vendor. An extension of the restricted time limit by cloud vendors will allow running the complete workflow using the serverless architecture with avoiding the scheduling problem.
Saeed et al. (Sat,) studied this question.