Serverless Effect on Node.JS Development
It's not simply because the front-end can easily construct servers in js that makes the front-end domain important. Personally, I believe its front-end engineering, which includes npm, commonjs, and a comfortable programming environment, is its greatest contribution.
It causes the front-end to start to evolve from a standard corporate application development methodology that is similar to slash-and-burn and traditional software engineering. Prior to now, resource references, dependency management, and module specifications had no efficient tools or standards.
You can never understand the everything but you can push yourself to understand the system!
Ryan Dhal (Creator of Node.js )Instead, package-based and npm-based package deployment and dependency management became commonplace once Node JS gained popularity . The world's largest package management warehouse, npm, is now used for front-end project package management. It includes a number of cli tools based on Node JS development that are auxiliary to front-end development (such as grunt, gulp).
Is Serverless going to have an impact on frontend?
Although the front end has been associated with serverless, many individuals have not yet Perception Following that, the serverless display will have a significant impact on the front end, primarily in three areas. The refinement of the social division of labour. Prior to it, there was no such thing as a front-end development role, which was commonly referred to as a web engineer or a website engineer.
A front-end engineer with a focus on the browser and mobile progressively emerged due to the UI's good interoperability and experience. The front-end technology market, however, has steadily stabilised. Numerous out-of-the-box libraries, vertical solutions, and engineering techniques are available to you thanks to more than 10 years of development.
The bond of FrontEnd and Serverless
web engineers would pass js resources and view files (which may be static or dynamic). Server, at that time, the front end needs to care about the server, but the popularity of cdn and return source policies, the large-scale use of engineering and building systems, so that the front end can quickly throw a js or static file to the cdn node, through the source mechanism (cdn Back to the source of a dynamic service) semi-dynamic view layer rendering is also possible in this whole process the front-end development does not need to care about any server knowledge.
Do not know how many nodes cdn, how to do load balancing, do gslb, also Do not need to know how much qps, a cdn can put a variety of business development resources, it can be said that cdn is the pioneer of the serverless concept.
Implementing serverless in frontend cloud computing
The future cloud facilities will be very thick, very professional and stable, and front-end developers can quickly and cost-effectively build a business on cloud facilities. Logic Front end and front end of the server (for the entire request link, the front end is relative, as long as the role closer to the customer request can be called the front end), the division of labor will be less clear, the front end of the previous browser will Gradually taking part in the server-side access layer and the bff layer, returning to the original, returning to the role of the web development engineer in history, this is the biggest change to the front end.