Both are hot topics in today's technological age, it has been seen as a competitor to develop technology.
First of all, there are quite a lot of curiosity and fear. In addition, both of which are available for engineers to use, efficient, machine-independent abstraction.
However, between the champion, there is an insurmountable gap. You're either in the container area, or select Serverless. In addition, if you are willing to combine the two, it would be a powerful combination.
Is expected to 2021, Serverless will reach US $ 7.72 billion in size. But the demand for container will also increase by 40% .
1. What is the Serverless?
In short, Serverless is running on the server, based on a subset of cloud services.
1.1 container vs. Serverless:. Why Serverless better?
Infrastructure demand service provider or supplier management Serverless operation. All you need to do is deploy code. So, you have the opportunity to focus more on application logic, without having to worry about infrastructure.
The technology in the mainstream business is very cool kind of existence.
Source: https://www.slideshare.net/speckandtech/a-bot-in-minutes-with-serverless
There are many available platforms - Google cloud, AWS the Lambda, EdgeEngine
2. Why should Containers to Serverless?
2.1 Cheap
Use Serverless, you usually pay-per-use. Price idle resources will be exempt. For example, Lambda range of 100 ms for time unit.
Further, since the task is small, and run on a small Serverless function, thus overhead cost can be minimized.
2.2. Low maintenance
In addition, the code deployment, container configuration, system policies, the availability level or back-end server tasks, you are no longer a headache.
You have the opportunity to try automatic scaling capacity.
2.3. Simple Prototype
Source: epsagon.com
In the host application environment, Serverless is an external integration. Therefore, the life cycle of the individual circumstances of any vessel can avoid run-time failures.
3. Use Serverless occasions what?
3.1. Sites or applications background tasks
Like other servers, Serverless receive information from a database or front-end program and site. According to a program to retrieve data and returns it to the user interface.
Compared with the container, pricing differences Serverless that it depends on the actual billing backend task execution duration.
3.2. Mass daemon
In the sales system, Serverless functions can be organized ad hoc tasks and inventory restocking transaction database and so on.
Last but not least is, Serverless in converting the data to persistent storage or analysis will be forwarded to the index service is very convenient.
4. Serverless restriction
These limitations occur in size and memory usage, or is based restrictions Serverless architecture.
For example, in order to maintain the normal operation function and prevent additional consumption of system resources, a limited list of programming languages native support for Serverless is not natural. Due to limitations of the basic functions, Serverless function may not be suitable for monitoring tools. First, Serverless external support for mainframe integration platform.
Therefore, you can not access the content management systems.
5. What is the micro container service?
It's just a separate package of a part, in which the deployment, execution and expansion of an application.
According to Amazon's introduction of the container is "an operating system virtualization approach that allows users to run applications in the process of resource isolation."
The container frame, Docker saying, container management platform statement:. "Vessel is a software unit, it will all depend on the code and its packaged together, so that applications can be quickly and reliably migrate from one environment to another."
During migration from one environment to another, the container concept is very useful. The reason lies in its isolation can be introduced during the migration, in order to avoid changing any variable.
So, if you want to design a product code migration from development to production, which will be prepared for you.
6. The container vs. Serverless: Why container?
A lot of advantages.
6.1 container vs. Serverless:. Container large-scale power projects
If you have expertise in this area, then you will enjoy using container. It is most suitable for a wider range of applications or business. In this case, use Serverless, you may soon face the problem of the spread of the code and difficult to manage.
For example, if the application runs on the Serverless, the refractor bottlenecks occur. The result will be an extremely decentralized micro-services.
6.2 container vs. Serverless:. Full control Docker
You can set policies, retention and management of resources, and strictly control the security and make full use of container management and migration services.
Infrastructure commands all rests in your hands, just on-demand can be.
6.3 container vs. Serverless:. Debugging, testing, and monitoring
Switch state of the container and manually browse activity.
This ensures effective in-depth debugging and testing, comprehensive use of resources, as well as in-depth performance monitoring at all levels.
7. Where the benefits of container in?
The first and most important benefit is "unique and easy portability." You can rely on all applications and all combinations and run it anywhere in a small package in.
Container is ideal for large-scale applications, because it is not memory or size limit. Here you are the sole owner of all involved functions.
8. Compare the container without service operator vs.
To compare the difference between the container and Serverless calculation.
Container most suitable for large and complex applications. If your product is environmentally sensitive, you need to meticulous quality assurance and control, container is the solution.
Single container when migrating legacy applications is also very convenient. You can organize this large applications debris container, and use third-party tools for installation.
Container for large electricity provider website. That has considerable site map or site has many sub-domains. You can use the container in which each node package.
Therefore, if you want to start a new project, and the product does not require much migration, Serverless is the best choice. For example, Serverless things is the best choice (the IoT) applications. The application to monitor the presence of water, water storage facilities to identify leaks.
Typically, the program does not have to be running, but the case of leakage, which need to be ready to perform.
Normally, when the development speed and cost minimization is very important, and do not want the management of scalability, Serverless is the ideal choice.
9. Mixed Model
Do you still insist to choose between the container and the Serverless?
As of now, both can be used for the same development project, but for different purposes. Serverless apply to data processed by the trigger event-driven. On the other hand, the container provides greater scalability and independence in the specification.
With proper knowledge, you can pass small pieces of container management projects, as a way to run a subset of the project on the Serverless.
But it depends on budget management and project requirements.
in conclusion
Container and non-server computing? ! ! As they say, these are competing technology! !
Calculated based on the container and the server is contemporary no. They support the development of cloud-based software and world continuous delivery. So, if you are seeking cloud strategy, then the integration of technology to mitigate the weaknesses in your favor.
Which side are you? Would you consider it will combine the two?
Original: https://geekflare.com/containers-vs-serverless/
Zuo_zhe: Pallavi Priyadarshini
Translator: Wan wanted
September welfare, public concern number backstage reply: 004, receive translations in August highlights! Go on welfare Re: 001, 002, 003 can receive!
