Summary: Open source is just the beginning, the end is far from here! From microservices open source to Serverless open source, we are continuing to open ali precipitation’s technical capabilities. However, the difference this time is that with the release of Serverless capability, the front-end will enter a new era, just write a few functions to realize back-end business logic, promote the rapid online business, so that the whole front-end research and development efficiency is greatly improved.
Open source is just the beginning, the end is far from here.
From microservices open source to Serverless open source, we are continuing to open ali precipitation’s technical capabilities. However, the difference this time is that with the release of Serverless capability, the front-end will enter a new era, just write a few functions to realize back-end business logic, promote the rapid online business, so that the whole front-end research and development efficiency is greatly improved.
What is Mindway Serverless
Since the release of V1.0 in early July, Midway Serverless has earned over 2.7K STARS. Midway Serverless is a Serverless solution consisting of four parts: Framework, runtime, toolchain, and configuration specification. When combined, these four parts provide some unique Serverless capabilities:
1. Easier migration between platforms by providing uniform configuration specifications and entry smoothing mechanisms so that code is basically the same on each platform; Extend the runtime apis of different cloud platforms to not only load common inter-platform extensions, but also access private deployment solutions within the company.
2, make the application easier to maintain and expand to provide a standard cloud platform function input parameter event definition; Provide multiple sets of community front-end React, Vue and other integrated development schemes; We use TypeScript as the base language for extensions and definitions. Provides a comprehensive dependency injection solution that is the hallmark of the Midway system.
3. Eco-lighter and free-function architectures reuse KOA’s eco-and Web middleware capabilities, making it easier to deal with traditional Web; Provide egg component reuse egg plug-in ecological chain, enterprise development link is more simple and smooth; The unification of the Midway architecture’s decorator capabilities makes traditional Web migration to a Serverless architecture faster and better.
Anti-platform lock
Vendor Lock-in is a question that torments the soul of everyone who uses a cloud platform. Midway Serverless’s original intent was to have a single set of code that could run on different platforms and runtimes. We don’t recommend customizing runtimes without knowing the whole picture. In fact, the official runtime is the most stable and certainly the best performing, and all benchmark runs are based on that.
The first question most companies we know about Serverless is, does my code have to be tied to Alibaba Cloud, Tencent Cloud, AWS, etc.
Faced with this problem, Midway Serverless provides a set of “hidden” portals with generic definitions to solve this problem.
For each platform, Midway Serverless provides different runtime initiators to smooth out platform differences and regularize platform entry and exit parameters, event structures, and gateway return formats so that users are as unaware of differences in underlying containers and protocols as possible.
In addition, Midway Serverless provides a set of Spec definitions that smoothen the differences between platforms while making it easy to reuse the same toolchains and functional logic across multiple platforms.
In this way, both API Gateways and plain HTTP triggers can provide apis on a single programming plane, making writing code easier.
The front can assign
Cloud + development experience is one of Midway Serverless’s goals, traditional application development, front-end/back-end separation, multi-warehouse development, deployment separation. Even with node.js’s glue layer, there is no way to avoid the fragmentation of human development motion. In a Serverless system, this is not a problem.
Due to the simplification of the backend, coupled with the BaaS of cloud services, data aggregation and page rendering become easier, and the front-end can be used and developed faster.
Integration has gradually become the front-end appeal of this area. The so-called integration is not only the integration of traditional warehouse, but also the evolution of the whole development mode, and the opportunity to reshape the whole system of CI/CD from engineering system to code.
Today, Midway Serverless provides an integrated front-end development solution that incorporates the existing React and Vue ecosystem, as well as customized solutions for the entire tool chain (Webpack, Ice Scrips, UMI, etc.). Blogs, for example, also provide out-of-the-box solutions.
As for the detailed front – and back-end integration capabilities, we will write a separate article later on the details and thinking of front-end integration.
Applications and functions
Serverless is the direction for some time to come and the paving brick for the front end to move to a higher level.
I have been thinking about the relationship between the end state of functional development and applications.
At the present stage, our answer is to unify. After countless soul questioning and user demand questioning, we have come to this answer, function is the smallest embodiment of the application in the current business, more simply, it is part of the code running the application in the smallest specification container.
In the following period of time, we will focus on the access of more platforms and the migration scheme of traditional applications, so that the former users can also enjoy the dividend of Serverless flexibility, so that the cost of enterprises is lower and the business is easier to go online.
Community and the future
Under the background of the deepening of Ali’s large, medium and small front-end business architecture, node.js saw the future in the end-to-end business delivery scenario last year with the help of its cloud native /Serverless development.
The new generation of front-end business delivery mode of cloud + terminal has gradually become a reality, which can help the technical team to shape special forces with overall business delivery ability and help the business win quickly. However, there is still a long way to go. In order to reach this stage as soon as possible, we need to focus on two core issues: 1. Scale cost, 2. Speed of delivery.
We expect the Node.js/Serverless system to be fully advanced in the future through our continued investment in scale cost and speed of delivery.
Ecosystem:
Author: Chen Zhongyin
The original link
This article is the original content of Aliyun and shall not be reproduced without permission.