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

This article mainly explains "what are the advantages of Serverless architecture". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn what are the advantages of Serverless architecture.

What is Serverless, like many new concepts, Serverless currently does not have a generally accepted and authoritative definition. The latest definition goes like this: "serverless architectures are Internet-based systems in which application development does not use regular service processes. Instead, they rely only on third-party services (such as AWS Lambda services), a combination of client logic and service hosting remote procedure calls." At first, the "serverless" architecture tried to help developers get rid of the setup and management of server devices needed to run back-end applications. The goal of this technology is not to achieve "serverless" in the true sense, but that the third-party cloud computing provider is responsible for the maintenance of the back-end infrastructure, providing developers with the required functions in the form of services, such as databases, messages, and authentication. In a nutshell, the purpose of this architecture is to let developers focus on the running of the code without managing any infrastructure. The program code is deployed on a platform such as AWS Lambda to trigger calls to functions through event-driven methods. Obviously, this is an architectural technology that is entirely aimed at programmers. Its technical features include event-driven call mode and limited program running mode. For example, the running time of AWS Lambda function is 3 seconds to 5 minutes by default. From the perspective of the emergence of this architecture technology for more than two years, this technology has been widely used, such as the back-end of mobile applications and Internet of things applications. In short, the emergence of serverless architecture is not to replace traditional applications. However, in view of the highly flexible usage patterns and event-driven features, developers / architects should pay attention to this new computing paradigm, which can help us reduce deployment, improve scalability, and reduce the maintenance burden of the infrastructure behind the code. The concept of Serverless's historical Serverless is not easy to understand. At first glance, it is easy to confuse hardware servers and software services with what they call "servers". The so-called "serverless" emphasized here means that our code will not be explicitly deployed on specific software or hardware servers. The environment in which code hosting runs is provided by cloud computing vendors such as AWS. The first time the word Serverless was used was an article called "Why The Future of Software and Apps is Serverless" written by Ken Form in 2012. This article is about continuous integration and source code control, not the architectural model we specifically refer to today. But Amazon's release of AWS Lambda in 2014 takes the "Serverless" paradigm to a whole new level, providing a new system architecture for applications running in the cloud. Instead of constantly running the process on the server waiting for HTTP requests or API calls, you can trigger code execution through some event mechanism, which usually requires a simple function to be configured on a server in AWS. Since then, Ant Stanley named "Server are Dead …" in July 2015. The article explains his idea of Serverless, "Server are dead … they just don't know it yet" around AWS Lambda and the just released AWS API Gateway. In October 2015, at the AWS re:Invent conference that year, the concept of Serverless appeared repeatedly on many occasions. The impression includes the speeches "(ARC308) The Serverless Company Using AWS Lambda" and "(DVO209) JAWS: The Monstrously Scalable Serverless Framework". With the further fermentation of this concept, the first Serverlessvconf was held in London in October 2016. In two days, more than 40 speakers from around the world shared with developers about the progress in this field. AWS plays a very important role in the world of Serverless. But AWS is not the only provider of Serverless architecture services. Other vendors, such as Google Cloud Functions, Microsoft Azure Functions, IBM OpenWhisk, Iron.io, and Webtask, offer similar services on various open source platforms.

Serverless and Faas Micro Services (MicroService) are another hot topic in the software architecture domain industry. If microservices are based on small functional blocks that focus on a single responsibility and function, and compose complex large applications in a modular way, then we can further think that Serverless architecture can provide a more "code fragmentation" software architecture paradigm, we call it Function as a Services (FaaS). The so-called "Function" provides smaller program units than micro-services. For example, the code needed to perform all the CRUD operations for a customer can be performed by a micro-service representative, and the "functions" in FaaS can represent every operation that the customer wants to perform: create, read, update, and delete. When the "create account" event is triggered, the corresponding "function" is executed by the AWS Lambda function. In this sense, we can simply equate the Serverless architecture with the FaaS concept.

The comparison between FaaS and PaaS at first glance, the concepts of FaaS and PaaS have many similarities in some ways. People even think of FaaS as another form of PaaS. But Mike Roberts, vice president of engineering at Intent Media, has a different view: "most PaaS applications cannot start and stop the entire application for every request, and the FaaS platform is born to achieve this purpose." The biggest difference between FaaS and PaaS in operation and maintenance is the scaling ability. For most PaaS platforms, users still need to consider scaling. But for FaaS applications, this problem is completely transparent. Even if the PaaS application is set to zoom automatically, it still cannot be scaled at the specific request level, and the FaaS application is much more cost-effective. Adrian Cockcroft, vice president of cloud architecture strategy at AWS, once gave a simple way to define the two: "if your PaaS can effectively start an instance and run it in half a second in 20 milliseconds, you can call it Serverless."

The advantages of Serverless architecture reduce operating costs: Serverless is a very simple outsourced solution. It allows you to delegate a service provider to manage servers, databases, applications and even logic, otherwise you will have to maintain it yourself. Because the number of users of this service will be very large, there will be economies of scale. The cost reduction includes two aspects, namely, the cost of infrastructure and the cost of personnel (operation / development). Reduce development costs: IaaS and PaaS exist on the premise that server and operating system management can be commercialized. The result of Serverless as another service is that the entire application component is commoditized. Scalability: an obvious advantage of the Serverless architecture is that "scale-out is fully automated, resilient, and managed by service providers." The biggest benefit of benefiting from basic infrastructure is that you only need to pay for the computing power you need. Simpler management: the Serverless architecture is significantly simpler than other architectures. Fewer components means less administrative overhead. "Green" calculation: according to Forbes magazine, the typical server in business and enterprise data centers provides only 5% to 15% of the average maximum processing power output. This is undoubtedly a huge waste of resources. With the advent of Serverless architecture, let service providers provide our computing power to meet real-time needs to the maximum extent possible. This will enable us to use computing resources more efficiently.

Serverless architecture paradigm Mobile Application background Serverless reference Architecture Real-time File processing Serverless reference Framework Web Application Serverless reference Framework Internet of things Application background reference Architecture Real-time streaming Serverless reference Architecture Thank you for your reading, this is the content of "what are the advantages of Serverless architecture". After the study of this article, I believe you have a deeper understanding of the advantages of Serverless architecture. The specific use situation still needs to be verified by practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.