Serverless computing is a cloud computing execution model in which the cloud provider dynamically manages the allocation of machine resources. Pricing is based on the actual amount of resources consumed by an application, rather than on pre-purchased units of capacity. It is a form of utility computing.
Serverless computing still requires servers, hence it's a misnomer. The name "serverless computing" is used because the server management and capacity planning decisions are completely hidden from the developer or operator. Serverless code can be used in conjunction with code deployed in traditional styles, such as microservices. Alternatively, applications can be written to be purely serverless and use no provisioned servers at all.
Video Serverless computing
Serverless runtimes
Most serverless vendors offer compute runtimes, also known as function as a service (FaaS) platforms, which execute application logic but do not store data. The first "pay as you go" code execution platform was Zimki, released in 2006, but it was not commercially successful. In 2008, Google released Google App Engine, which featured metered billing for applications that used a custom Python framework, but could not execute arbitrary code.
AWS Lambda, introduced by Amazon in 2014, was the first public cloud vendor with an abstract serverless computing offering. AWS Lambda initially supported only Node.js. It now supports Python, Java, C# and Go, and code written in other languages can be invoked indirectly via Node.js.
Google Cloud Platform offers Google Cloud Functions, which supports Node.js by now.
IBM has published OpenWhisk as an open source serverless platform. OpenWhisk includes native support for Node.js, Python, Java, and Swift, and supports other languages and runtime via Docker containers.
Microsoft Azure offers Azure Functions, which is offered both in the Azure public cloud or on-premises via Azure Stack.
Maps Serverless computing
Serverless databases
Several serverless databases have been released. These systems extend the serverless execution model to the RDBMS, eliminating the need to provision or scale virtualized or physical database hardware.
Azure Data Lake is a highly scalable data storage and analytics service. The service is hosted in Azure, Microsoft's public cloud. Azure Data Lake Analytics provides a distributed infrastructure that can dynamically allocate or de-allocate resources so customers pay for only the services they use.
Google Cloud Datastore is an eventually-consistent document store. It offers the database component of Google App Engine as a standalone service. Firebase, also owned by Google, includes a hierarchical database and is available via fixed and pay-as-you-go plans.
FaunaDB is a globally distributed, transactional database, based on technology from Twitter. It spans multiple public cloud providers with pay-as-you-go pricing, and is also available on-premises.
Amazon Aurora Serverless is an on-demand auto-scaling configuration for Aurora where the database will automatically start-up, shut down, and scale up or down capacity based on your application's needs.
Advantages
Cost
Serverless is more cost-effective than renting or purchasing a fixed quantity of servers, which generally involves significant periods of underutilization or idle time. It can even be more cost-efficient than provisioning an autoscaling group, due to more efficient bin-packing of the underlying machine resources.
This can be described as pay-as-you-go computing or bare-code as you are charged based solely upon the time and memory allocated to run your code; without associated fees for idle time.
Immediate cost benefits are related to the lack of operating systems costs, including: licences, installation, dependencies, maintenance, support, and patching.
Operations / Scalability
In addition, a serverless architecture means that developers and operators do not need to spend time setting up and tuning autoscaling policies or systems; the cloud provider is responsible for seamlessly scaling the capacity to the demand.. As Google puts it: 'from prototype to production to planet-scale.'
Small teams of developers are able to run code themselves without the dependence upon teams of infrastructure and support engineers; more developers are becoming DevOps skilled and distinctions between being a software developer or hardware engineer are blurring.
Productivity
With Function as a service, the units of code exposed to the outside world are simple functions. This means that typically, the programmer does not have to worry about multithreading or directly handling HTTP requests in their code, simplifying the task of back-end software development.
Disadvantages
Performance
Infrequently-used serverless code may suffer from greater response latency than code that is continuously running on a dedicated server, virtual machine, or container. This is because, unlike with autoscaling, the cloud provider typically "spins down" the serverless code completely when not in use. This means that if the runtime (for example, the Java runtime) requires a significant amount of time to start up, it will create additional latency.
Resource limits
Serverless computing is not suited to some computing workloads, such as high-performance computing, because of the resource limits imposed by cloud providers, and also because it would likely be cheaper to bulk-provision the number of servers believed to be required at any given point in time.
Monitoring and debugging
Diagnosing performance or excessive resource usage problems with serverless code may be more difficult than with traditional server code, because although entire functions can be timed, there is typically no ability to dig into more detail by attaching profilers, debuggers or APM tools. Furthermore, the environment in which the code runs is typically not open source, so its performance characteristics cannot be precisely replicated in a local environment.
Security
Serverless is sometimes mistakenly considered as more secure than traditional architectures. While this is true to some extent because OS vulnerabilities are taken care of by the cloud provider, the total attack surface is significantly larger as there are many more components to the application compared to traditional architectures and each component is an entry point to the serverless application. Moreover, the security solutions customers used to have to protect their cloud workloads become irrelevant as customers cannot control and install anything on the endpoint and network level such as IDS/IPS.
Serverless frameworks
Serverless frameworks are designed to make it easier to build, test, and deploy serverless applications. Some prominent ones are:
- Serverless Framework, for creating serverless applications deployed to AWS Lambda or Azure Functions with Node.js and Python.
- SLAppForge Sigma, an IDE with a hybrid model between the drag-and-drop style development, and raw code for serverless application development, testing and deployment on AWS supporting NodeJS.
- Kubeless, a proof of concept to develop a serverless framework for Kubernetes.
- Fission, a framework for serverless functions on Kubernetes, supporting Python, NodeJS, Go, C#, and PHP.
- Up, an open-source tool for deploying regular HTTP servers (such as Go net/http) to AWS Lambda.
- Nuclio, an open-source framework that runs up to 400,000 invocations per second.
- OpenFaas, an open-source framework for building serverless functions with Docker and Kubernetes which has first class support for metrics.
- Fn Project, an open-source and container-native serverless platform that can be run on cloud environments or on-premise
- The AWS Serverless Application Model | (AWS SAM), a model provided by Amazon Web Services to define serverless applications.
References
Further reading
- Roberts, Mike (25 July 2016). "Serverless Architectures". MartinFowler.com. Retrieved 30 July 2016.
- "Creating full-stack Serverless applications on the AWS platform". Serverless-Stack.com. Retrieved 5 April 2017.
- Kimhi, Tal (7 June 2017). "The State of The Serverless Ecosystem". Medium. Retrieved 15 September 2017.
- Jamieson, Frazer (4 September 2017). "Losing the server? Everybody is talking about serverless architecture". BCS, the Chartered Institute for IT. Retrieved 7 November 2017.
Source of article : Wikipedia
0 Comments