be relative to BGP server What is the defect of serverless itself? Although there are many advantages of no server, nothing is absolute. No matter how perfect the product is, there will be flaws. The problem is that the server free model itself has problems. Please do not misunderstand. I'm not saying that the serverless model itself is bad, or in some cases it can't provide considerable value for a particular company. But serverless will quickly replace the core idea of the "revolution" of the existing architecture. Then relative to BGP The server, nothing The server What are the defects of our own? It is believed that everyone does not particularly understand it, so today, Micronet will take you to study it, hoping to let you know more about serverless. Compared with BGP server, Micronet believes that serverless defects mainly include the following.
1. Limited programming language
Most serverless platforms only support applications written in specific languages. Compared with BGP server, this severely limits the agility and adaptability of the system.
Of course, most serverless platforms support most major programming languages. AWS Lambda and Azure Functions also provide wrapper functions, enabling you to run applications and "functions" in languages not supported by the system. Therefore, language restrictions in most institutions have no effect in most cases. But that's the problem. One of the advantages of the serverless model is that it supports non mainstream and infrequent programs to run more easily. You only need to pay for the running time of the program. These non mainstream and infrequently used programs are written in obscure programming languages that are infrequently used. This results in one of the main advantages of the serverless model not working properly.
2. No server lock supplier
The second problem with serverless platforms (or at least from the current implementation mode) is that there are almost no similar platforms at the operational level. There are almost no cross platform standards for the creation, deployment and management of "functions". In other words, it takes a lot of time to migrate "functions" from one vendor specific platform to another.
The biggest difficulty of migrating to no server is that it is usually not the calculation "function" of some code fragments. This is the opposite of the cheap agile platform promised without servers.
Some people can only claim that the serverless model is a new concept, and there is no time to standardize the way of work. But as mentioned above, serverless is not a new concept. In addition, many other cloud based technologies, such as containers, improve availability by developing and widely adopting strong community-based standards.
3. No server performance problem
The computing performance of serverless platforms is difficult to measure. Part of the reason is that companies that provide these services may hide this information in part of their vested interests. Most service providers claim that if there is no inevitable delay problem, "functions can be run at the same speed as internal servers" on remote serverless platforms.
However, some factual evidence has drawn diametrically opposite conclusions. If the Function has not run on a specific platform before, or has not run for a period of time, initialization may take some time. This may be because these codes are migrated to a storage medium that is not frequently accessed. Like performance statistics, most serverless computing vendors do not disclose the specific situation in this regard.
Of course, there are many solutions to this problem. One way is to optimize "functions" using cloud based languages running on serverless platforms. However, this has damaged the "agility" advocated by the platform to some extent.
Another method is to often run programs with high performance requirements on the schedule to maintain "freshness". Of course, considering that users will pay for the normal running time of the program, this method contradicts the claim that serverless platforms are more cost-effective. Cloud service providers have introduced new methods to reduce cold start, but the original intention of FaaS has been undermined because many providers need to "reduce to one" model.
The serverless system running internally can reduce the "cold start" problem, but this method itself introduces additional costs, which is only a small choice for resource rich teams.
4. Unable to run the entire application without server
Why doesn't serverless architecture quickly replace existing models? Finally, one of the most important reasons is that users often cannot run an entire application on a serverless system.
More precisely, it can be done, but it is not cost-effective. A well functioning single application should not be a series of "functions" connected to 8 gateways, 40 queues, and dozens of database instances. Therefore, serverless is suitable for areas that have not yet been developed. Existing applications (architectures) are rarely migrated. Therefore, you can migrate, but it is recommended to start from 0.
In other words, in most cases, serverless platforms complement internal servers to perform tasks that require a lot of computing resources. This makes serverless and container, virtual machine and other basic cloud technologies very different. Both support complete remote computing. This is the difficulty of switching from microservice to serverless.
Of course, this is not necessarily a problem. Many organizations sometimes use a lot of computing resources and do not need to purchase the hardware needed to implement functions internally. No server can really and continuously take advantage. However, partially managing the running of applications running on serverless cloud architecture on internal servers will bring another layer of complexity to application deployment.
The above is the problem of what defects exist in the serverless itself analyzed by Micronet, and I hope it can help you. Neutronic BGP Server virtual host renting, rapid deployment, multiple line options, support for partitioned dedicated lines, T-level bandwidth, and can provide various customers with better IDC services. Micronet is an IDC service provider focusing on BGP server and virtual host rental and hosting. With more than ten years of industry experience, it is safe, stable, reliable and reassuring. It is a leading enterprise in the domestic IDC industry. It helps thousands of enterprises to achieve network informatization, 7 * 24 hours of manual service, after-sales care free, and reputation.
BGP server: hopechilam.com
