Home Blog Talks

FaasJS 2021 year-end review and new year outlook


2021 Year-End Review

2021 is coming to an end. FaasJS has iterated 150 versions in the past year, mainly making efforts in three directions:

  1. Fully enable the hook style interface form, making the use of plug-ins more flexible and convenient.
  2. The deployment command line has been greatly optimized, supporting features such as parallel publishing, publishing only updated files, and automatic retry on failure.
  3. The official plug-ins have been streamlined, and plug-ins that do not comply with the atomic development and design philosophy have been removed, such as TypeORM, etc.

In addition to the above three directions, there are also a large number of detailed improvements, which I will not go into details here. Interested students can check the update log.

At the same time, this year FaasJS also launched the official Docker image library and VS Code plug-in to facilitate development and deployment.

Outlook 2022

Since FaasJS has reduced the cost of back-end development to a very low level, for example, in Baobaoshe, junior programmers can efficiently iterate complex ERP systems containing hundreds of process links.

In the front-end field, development costs remain high due to different terminals and interfaces. Therefore, in the next year, I will focus on reducing front-end development costs.

Currently we plan to work in the following directions (tentative):

  1. In the Web and App fields, React provides modules and interfaces that are closer to the business layer, making it easier and more intuitive for the front-end interface to call the back-end.
  2. In the field of mini programs, developing relevant modules and interfaces based on Uni App greatly reduces the development cost of mini programs.
  3. Develop a business component library based on Ant Design to greatly simplify CRUD development costs.
  4. Develop an integrated type definition tool based on Typescript, allowing the front and back ends to use the same set of type definitions, reducing communication costs and error rates.

In the backend area, I will strengthen the support of FaasJS single application mode for use in non-Serverless environments.

If you are interested in the above directions or have other ideas, you are welcome to participate in the discussion and development of FaasJS, so that we can work efficiently and live happily.

Back to all posts