Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about how to understand the value of Serverless. Many people may not understand it very well. In order to make you understand better, the editor has summarized the following contents for you. I hope you can gain something according to this article.

Although it is said that Serverless, but the Server (server) can not really disappear, the less in Serverless, rather, it should mean that developers do not care about the server. This is like modern programming languages Java and Python. Developers do not need to allocate and release memory manually, but the memory is still there, but it is managed by the garbage collector. Calling a platform that can help you manage your servers as Serverless is like calling Java and Python the Memoryless language.

However, if we look at today's era of the cloud, then Serverless cannot be narrowly understood as not caring about the server. In addition to the basic computing, network and storage resources contained in the server, resources on the cloud also include various types of upper-level resources, such as databases, caches, messages, and so on.

The Vision of Serverless

In February 2019, the University of UC Berkeley published a paper entitled "Cloud Programming Simplified: A Berkeley View on Serverless Computing", which also contains a very clear and vivid metaphor, which is described as follows:

In the context of the cloud, Serverful computing is like programming in low-level assembly language, while Serverless computing is like programming in a high-level language such as Python. For a simple expression such as c = a + b, if it is described by assembly, you must first select several registers, load the values into the registers, do mathematical calculations, and then store the results. This is like today's Serverful computing in the cloud environment, developers need to allocate or find available resources first, then load code and data, then perform calculations, store the results of calculations, and finally manage the release of resources.

The so-called Serverful computing in this paper is the mainstream way we use the cloud today, but it should not be the way we use the cloud in the future. I think the vision of Serverless should be Write locally, compile to the cloud, that is, the code only cares about business logic, and the tools and clouds manage resources.

The value of Serverless

After having an overall abstract concept of Serverless, we also need to understand the main features of the Serverless platform, which are also the embodiment of the core advantages of Serverless.

1. Don't worry about the server.

Managing one or two servers may not be a hassle, but managing thousands or even tens of thousands of servers is not that easy. Any server may fail, how to automatically identify the fault and remove the problematic instances, this is the ability that the Serverless platform must have; in addition, the security patch upgrade of the operating system needs to be completed automatically without affecting the business; the log and monitoring system needs to be opened by default; the security policy of the system needs to be automatically configured to avoid risk When resources are insufficient, you need to be able to automatically allocate resources and install related code and configuration, and so on.

two。 Automatic elasticity

Today's Internet applications are designed to be scalable. When the business has obvious peaks and troughs, or when the business has temporary capacity requirements (such as marketing activities), the Serverless platform can achieve automatic elasticity in a timely and stable manner. In order to achieve this capability, the platform needs to have a very strong resource scheduling ability and a very keen perception of application indicators (such as load, concurrency).

3. Billed by actual use of resources

The use of cloud resources by Serverful is billed by occupation rather than usage. For example, if a user buys three ECS sets on the cloud, no matter how much CPU and memory the user actually uses, he needs to pay the overall cost of the three ECS. In Serverless mode, users are paid according to the resources actually used, for example, when a request actually uses a 1core2g specification resource 100ms, then users only need to pay for the unit price of the specification multiplied by time (i.e. 100ms). Similarly, if users are using a Serverless database, they only have to pay for the resources actually consumed by query, as well as the resources for data storage.

4. Less code, faster delivery

Code based on Serverless architecture usually heavily uses back-end services to separate data, state management, and other content from the code; in addition, the more thorough FaaS architecture also gives the Runtime of the code to the platform management. This means that for the same application, there will be much less code in Serverless mode than in Serverful mode, so it will be faster from distribution to startup. The Serverless platform can also provide very mature features such as code build and release, version switching and so on, which can improve the delivery speed.

After reading the above, do you have any further understanding of the value of Serverless? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.