Low-code (5) Low-code platform front-end technology component selection 3.0

  • Micro front-end framework selection

Currently, the excellent micro-frontend frameworks include qiankun, MicroApp, and single-spa; single-spa listens to the url change event, matches the rendered sub-application when the route changes, and renders it. This idea is also the mainstream way to implement micro-frontends . At the same time, single-spa requires sub-applications to modify the rendering logic and exposes three methods: bootstrap, mount, and unmount, which correspond to initialization, rendering, and unmounting respectively, which also requires sub-applications to modify the entry file. Because qiankun is packaged based on single-spa, these features are also inherited by qiankun, and some modifications to the webpack configuration are required.
Micro-app does not follow the idea of ​​single-spa, but draws on the idea of ​​WebComponent. Through CustomElement combined with a custom ShadowDom, the micro-frontend is encapsulated into a WebComponent-like component, so as to realize the componentized rendering of the micro-frontend. And because of the isolation feature of custom ShadowDom, micro-app does not require sub-apps to modify rendering logic and expose methods like single-spa and qiankun, and does not need to modify webpack configuration. It is currently the lowest cost of accessing micro-frontends on the market plan. The original hydrogen platform adopts two frameworks of micro-app and qiankun.

  • RPA technology selection

The hydrogen source platform integrates RPA tools to meet business development in some automation scenarios. Excellent RPA manufacturers include Microsoft PowerAutomate and UIpath in foreign countries, and Shadow Knife in China.
After trying out these products, I finally decided to integrate PowerAutomate and UIpath.

  • Map plug-in selection

    Map operations include AutoNavi, Baidu, and Tencent, but because the previous projects used AutoNavi, the platform is currently integrated with AutoNavi, and it will be expanded later as needed.

  • Is the web version of webIde technology selection
    vscode the best choice for webIDE? The team went to research and integrate vscode, but gave up after 1 month, because the web version of vscode requires different tenants to have different docker containers. As a small company, the cloud resources are very limited, so we can only give up this solution, and finally adopt github web compiler to implement online editing.

  • Is the web version of the front-end display framework
    vscode the best choice for webIDE? The team went to research and integrate vscode, but gave up after 1 month, because the web version of vscode requires different tenants to have different docker containers. As a small company, the cloud resources are very limited, so we can only give up this solution, and finally adopt github web compiler to implement online editing.

  • Others
    , such as display frame layout, skin switching, table display adaptation, etc., are self-developed.

This is all about the technical selection of the front-end related components, and the technical selection of the back-end will be introduced later

Guess you like

Origin blog.csdn.net/weiyongliang_813/article/details/130054651