CN115794093A - Micro front end implementation method based on multi-application fusion - Google Patents
Micro front end implementation method based on multi-application fusion Download PDFInfo
- Publication number
- CN115794093A CN115794093A CN202211604164.6A CN202211604164A CN115794093A CN 115794093 A CN115794093 A CN 115794093A CN 202211604164 A CN202211604164 A CN 202211604164A CN 115794093 A CN115794093 A CN 115794093A
- Authority
- CN
- China
- Prior art keywords
- application
- sub
- main
- applications
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a micro front end implementation method based on multi-application fusion, which comprises the following steps: developing a main application and a plurality of independent sub-applications; each sub-application registers with the main application, so that the main application has a sub-application registry; wherein the sub-application registry stores a sub-application ID of each sub-application and an application entry of the sub-application; and the master application manages the whole life cycle of each sub-application. The micro front end implementation method based on multi-application fusion provided by the invention has the following advantages: a plurality of independent web applications are fused into a micro front-end application, menus can be freely combined, data authorities can be freely distributed, and highly customized product service items can be provided for users.
Description
Technical Field
The invention belongs to the technical field of front-end architectures in cloud times, and particularly relates to a micro front-end implementation method based on multi-application fusion.
Background
In the early stage, the splitting and the combining of the huge stone application are realized in a mode of iframe nesting or direct jump of the sub-application, the advantage is that the natural sandbox is isolated, but obvious problems exist, such as the problem of white screen during application switching, the problem that data cannot be shared, and the like.
The 2014 industry provides a concept of micro front end, and with the appearance of Webpack, SPAs such as React and Vue are applied on a large scale, so that new problems are brought: the large-scale application of the megalithic stone requires resolution. In 2018, the first micro front-end open source tool single-spa is born, and mainly solves 2 problems, namely sub-application registration and sub-application life cycle management. Therefore, it is a combination of the sub-application loader and the state machine.
Specifically, the Entry configuration of each sub-application is registered on the micro front-end interface, the Entry configuration includes a sub-application name and an Entry JS file (JS Entry mode), the data transmitted to the sub-application by the main application is configured, and the activeWhen is configured to control whether to activate the sub-application by judging a matching routing state. By routing snoop related events, 3 important lifecycle hook functions are exposed: bootstrap (called before the sub-application is mounted to the page for the first time), mount (called when the sub-application is activated, logic such as mounting and page rendering of the sub-application is realized), and unmount (called when the sub-application is uninstalled, logic such as component uninstalling and event monitoring elimination is realized). When the main application manages the sub-applications, the sub-applications are mounted and uninstalled through the lifecycle functions exposed by the sub-applications.
The above micro front end architecture single-spa has the following significant problems:
1. the micro application loading method needs self maintenance, and the micro application is accessed in a JS Entry mode. Therefore, the whole sub-application needs to be packaged into a js bundle, and optimization means such as unpacking, css extraction, first screen loading and the like are hardly available; 2. there are side effects to application switching; 3. the problem of js and css sandbox isolation between applications; 4. sub-application preloading is not implemented; 5. inter-application communication problems.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a micro front end implementation method based on multi-application fusion, which can effectively solve the problems.
The technical scheme adopted by the invention is as follows:
the invention provides a micro front end implementation method based on multi-application fusion, which comprises the following steps:
step 2, the main application manages the whole life cycle of each sub-application, specifically:
step 2.1, the main application comprises a user login module, a layout module, a routing module and a global state sharing module;
step 2.2, when the main application receives user login information through the user login module, obtaining user authority according to the user login information, and pushing menu configuration according to the user authority; the menu configuration comprises sub-application IDs of a plurality of sub-applications which can be combined and are matched with the user authority; then, the main application receives the sub-application IDs of the plurality of sub-applications which need to be combined;
step 2.3, the main application combines a plurality of sub-applications which need to be combined to form a sub-application unit through the layout module;
step 2.4, the main application performs routing configuration on each sub-application through the routing module, including: configuring a path of a browser routing address url and an application entrance of each sub-application;
step 2.5, the main application switches and loads each sub-application by adopting the following mode:
the main application hijacks the routing address url of the browser, when the routing address url of the browser changes, the main application is matched with an application entrance of the corresponding sub-application according to the path corresponding to the routing address url of the browser determined in the step 2.4, and the corresponding sub-application is loaded according to the application entrance;
and 2.6, for the loaded sub-applications, the main application manages the whole life cycle from starting, mounting to destroying.
Preferably, step 2.6 specifically comprises:
and exposing related Hook functions in the life cycle change process of the sub-application, and adding additional functions on the corresponding hooks according to different service scenes.
Preferably, step 2.6 more specifically comprises:
routing skip is triggered by changing the routing address url of the browser, menu authentication and user identity authentication are carried out in a hook function before the routing skip, and if the token is expired, the browser skips to a login page to log in again;
after the sub-application acquires certain data, the data needs to be used as global shared data, and at this time, a new payload is transmitted by using a communication hook, and the global state is synchronously updated.
Preferably, sandbox isolation is used between sub-applications, and between a sub-application and a main application, and each sub-application has an independent execution context scope through the sandbox isolation.
Preferably, the main application has a sub-application state monitoring function, a sub-application state updating function and a sub-application state removing monitoring function;
performing state monitoring on each sub-application through the sub-application state monitoring function; when the change of the sub-application state is monitored, updating the state of the sub-application through a sub-application state updating function; and when the sub-application is unloaded, removing the monitoring function through the sub-application state, and moving the monitoring function and the updating function of the sub-application state to finish resource release.
Preferably, the global state sharing module is specifically configured to:
the main application stores the sub-application global state of all the sub-applications, and shares the sub-application global state of all the sub-applications to each sub-application through the global state sharing module.
The micro front end implementation method based on multi-application fusion provided by the invention has the following advantages:
a plurality of independent web applications are fused into a micro front-end application, menus can be freely combined, data authorities can be freely distributed, and highly customized product service items can be provided for users.
Drawings
FIG. 1 is a diagram of the architecture of a micro-front-end architecture of a multi-application fusion-based micro-front-end implementation method according to the present invention;
FIG. 2 is a routing diagram of a primary application to a secondary application provided by the present invention;
FIG. 3 is a flow chart of the master and slave application communication and state management provided by the present invention;
fig. 4 is a complete architecture diagram of a micro front end architecture of a micro front end implementation method based on multi-application fusion according to the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantageous effects solved by the present invention more clearly apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention provides a B/S structure-based multi-application-fused micro-front-end architecture implementation method, which belongs to the technical field of Web development. The main functions of the main application comprise authentication operations such as user login, logout, password modification, layout, routing authority and the like, and global shared Globalstate. After logging in, initializing to obtain the user authority related information, and generating a menu after filtering the routing authority. The sub-applications are completely independent individuals, are independently developed, independently deployed and independently operated, can be developed based on any frame library class, such as mainstream vue, spare and other spa applications, or based on jQuery and other old projects, and achieve relatively ideal compatible effects.
Specifically, the invention provides a micro front end implementation method based on multi-application fusion, which comprises the following steps:
step 2, the main application manages the whole life cycle of each sub-application, specifically:
step 2.1, the main application comprises a user login module, a layout module, a routing module and a global state sharing module;
step 2.2, when the main application receives user login information through the user login module, obtaining user authority according to the user login information, and pushing menu configuration according to the user authority; the menu configuration comprises sub-application IDs of a plurality of sub-applications which can be combined and are matched with the user authority; then, the main application receives the sub-application IDs of the plurality of sub-applications which need to be combined;
step 2.3, the main application combines a plurality of sub-applications which need to be combined to form a sub-application unit through the layout module;
step 2.4, the main application performs routing configuration on each sub-application through the routing module, including: configuring a path of a browser routing address url and an application entrance of each sub-application;
step 2.5, the main application switches and loads each sub-application by adopting the following mode:
the main application hijacks the browser routing address url, when the browser routing address url changes, the main application is matched with an application inlet of the corresponding sub-application according to the path corresponding to the browser routing address url determined in the step 2.4, and the corresponding sub-application is loaded according to the application inlet;
and 2.6, for the loaded sub-applications, the main application manages the whole life cycle from starting, mounting to destroying.
The step 2.6 is specifically as follows:
and exposing related Hook functions in the life cycle change process of the sub-application, and adding additional functions on the corresponding hooks according to different service scenes.
Step 2.6 more specifically comprises:
routing skip is triggered by changing the routing address url of the browser, menu authentication and user identity authentication are carried out in a hook function before the routing skip, and if the token is expired, the browser skips to a login page to log in again;
after the sub-application acquires certain data, the data needs to be used as global shared data, and at this time, a new payload is transmitted by using a communication hook, and the global state is synchronously updated.
In the invention, sandbox isolation is adopted between each sub-application and between the sub-application and the main application, and each sub-application has an independent execution context scope through the sandbox isolation.
In addition, the main application has a sub-application state monitoring function, a sub-application state updating function and a sub-application state removing monitoring function;
performing state monitoring on each sub-application through the sub-application state monitoring function; when the change of the sub-application state is monitored, updating the state of the sub-application through a sub-application state updating function; and when the sub-application is unloaded, removing the monitoring function through the sub-application state, and moving the sub-application state monitoring function and the sub-application state updating function to complete resource release.
The global state sharing module is specifically configured to:
the main application stores the sub-application global state of all the sub-applications, and shares the sub-application global state of all the sub-applications to each sub-application through the global state sharing module.
The following is a detailed description of the design concepts and principles of the present invention:
fig. 1 is a diagram of the basic architecture of the micro front end architecture. As shown in fig. 4, it is a complete architecture diagram of the micro front end architecture.
1. The user logs in the module to realize unified authentication, including menu authority, data authority, user basic information and the like of the user, the data storage can be in multiple ways, and according to different data characteristics, the data can be temporarily stored in a project store and can be subjected to interface real-time refreshing, and the data can also be locally stored for persistence, and the refreshed page data is not lost. The system is used as a user, provides personalized menu configuration, combines different sub-applications, allocates authority, and quickly meets personalized website building requirements by combining services;
2. after a user logs in, a new routing menu is generated after filtering according to routing authority, a layering technology is introduced on the basis of SPA, the browser address switching is taken over by the Base application to achieve the purpose of switching each sub-application, and meanwhile, the whole life cycle from starting to destroying of each sub-application is managed. Related Hooks functions are exposed in the life cycle changing process, and additional functions can be added to corresponding Hooks according to different service scenes. For example: (1) Routing skip is triggered when the address of the browser changes, menu authentication, user identity authentication and the like are carried out in a hook function before the routing skip, and if the token is expired, the browser skips to a login page to log in again; (2) After the sub-application A acquires certain data, the data is used as global shared data, a new payload can be transmitted by using a communication hook, and the global GlobalState is synchronously updated;
3. regarding the routing module, the Base main application needs to perform routing configuration on the micro application, specify a path corresponding to the url and an application entry, hijack a browser routing address, match a corresponding sub-application according to the path when the url changes, and load the corresponding sub-application according to the entry; the routing design is shown in fig. 2.
4. In order to avoid mutual pollution among the applications, JS sandbox isolation and CSS sandbox isolation are achieved inside the system. Each sub-application has its own independent execution context scope. Meanwhile, data persistence is realized by combining a state management tool, the main sub-application communicates with the sub-application, the sub-application communicates are indirectly realized, and the consistency of shared data is ensured.
At present, a special project exists in sub-applications, a web-based low-code visual editing generation system DVP can be realized, combination between a native script component inside the DVP and a main stream framework can be realized, a micro-front architecture can realize communication between the micro-front architecture and the native script component by exposing a specific Window object to the outside, in order to avoid polluting a global object, communication between the native script component and the outside needs to be realized, concepts of responsive programming and streaming are introduced, sending and monitoring events are realized by compiling a custom hook, a payload is transmitted, and asynchronous data streaming is supported. The consistency and integrity of the shared data are always maintained.
The CSS sandbox is internally realized through a Shadow DOM interface. The master application may also store one global CSS, which all the sub-applications share. At this point the CSS sandbox needs to be closed. The CSS sandbox isolation is realized by sub-applications in many ways, the vue realizes cs modularization, acts officers provide a cs in js method, or postcs, cs modules, project convention and other methods, so that whether the CSS sandbox is opened or not is determined according to actual requirements;
5. the sub-applications themselves are independently developed, deployed, and run. There may be its own independent State management State, internal event communication (vuex/reduce/mobx), etc. Unlike the normal project, only a little extra configuration needs to be made to the sub-applications to support the main sub-application merging.
During initialization, if the micro front-end architecture is supposed to operate as a sub-application, routing parameters, namely different browser addresses, need to be modified for matching and loading the corresponding sub-applications. Meanwhile, the globally shared GlobalState can be acquired through monitoring Hook (onglobalschange) exposed by a communication mechanism, and the Hook (setGlobalState) for sending the load realizes communication with other main and sub applications. If the micro front-end architecture is not adopted, no difference is generated with the common project;
as shown in fig. 3, a flow chart for communication and state management of the master and slave applications.
6. Regarding building deployments. The output contract is constructed in the form of umd lib. Deployment has no task limitation, and pm2 managed node applications can be realized by using web servers such as nginx or Apache, as long as normal access of the sub-applications is ensured. The Base application will automatically match the child application publishpath according to the browser address and load the corresponding child application.
The invention is a micro front end architecture system based on single-spa, which realizes the out-of-box use and can complete a multi-application fused micro front end application after simple API configuration and menu and data authority configuration.
The key technical points of the structure are as follows:
1. independent of technology stack
The sub-application technology stack has complete autonomy, mainstream front end frames such as React, vue, angular, jQuery and the like can be randomly selected, and the version is not limited, for example, vue2 or Vue, act15 or act16+ can be used for outputting umd format during construction;
2. independent development, independent deployment
The enterprise-level Web project is divided into small modules, all module warehouses are independent, multiple groups are developed in parallel, a set of common service component libraries are maintained by the multiple groups together, and all modules are deployed independently;
3. sandbox isolation
And (3) realizing the css sandbox:
the sandbox mode is internally realized through a Shadow DOM interface. The Web components have realized the encapsulation function, the Shadow DOM interface can attach a hidden and independent DOM to the specified element of the main container, the style isolation is realized originally, and the main stream browser supports the Shadow DOM, and vue project has no obvious problem;
if the sandbox mode is not opened, different frames have corresponding processing methods. 5363 a scanned instruction of vue framework style has already realized css modularization, and generates a unique attribute for an element after compiling, and the css style also adds an attribute prefix; and the act can avoid the global style pollution by means of css in js, css modules, prefix convention and the like.
Realizing a js sandbox:
scope isolation between sub-applications is achieved internally through the ProxySandbox sandbox. The main application proxies the window of each sub-application to generate a fakeWindow in a Proxy window mode. The window of the child application is proxied to the proxy object of the sandbox. Finally, a new scope chain is constructed. When the child application searches for the variable, the child application searches for the local fakeWindow first, and then searches upwards for the window of the main application, any change (addition, modification, deletion and the like) operation only aims at the local fakeWindow, other applications cannot be influenced, and the fakeWindow can be removed when the child application is unloaded. Operations on the window objects are completely isolated, and state isolation of the multi-instance mode is achieved. In a general scenario, only one active sub-application will exist at the same time.
4. Application communication
And realizing communication among a set of main and sub applications through a publish-subscribe mode. The main application defines the global state and executes an initialization method, and the method returns communication instance Actions, including methods of monitoring the global state, setting the global state, removing state monitoring and the like. The main application is transmitted to the sub-applications in a way of the prop, and the sub-applications receive the prop in the mount stage, so that the communication between the main and sub-applications is realized.
5. Resource preloading
For better user experience, the master application may specify the preloaded sub-applications when registering the sub-applications. The lifecycle of the single-spa is encapsulated secondarily in the framework, and the sub-applications have three important lifecycle hook functions (bootstrap, mount, unmount). And when the first sub-application mount (mount) is finished, loading the static resources of the specified sub-application, thereby avoiding blocking.
The invention has the beneficial effects that:
1. the enterprise-level Web application is divided into modules with specific functions, and each production and research line is independently developed and independently deployed. Old projects can be upgraded in new bins in an incremental mode, technical change is achieved, and the life cycle of products is also prolonged;
2. more optimization means are applied to a single sub, the packaging speed is higher, the size is smaller, and the time consumption for release and production is shorter;
3. a plurality of independent web applications are fused into a micro front-end application, menus can be freely combined, data authorities can be freely distributed, and highly customized product service items can be provided for users.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements should also be considered within the scope of the present invention.
Claims (6)
1. A micro front end implementation method based on multi-application fusion is characterized by comprising the following steps:
step 1, developing a main application and a plurality of independent sub-applications; each sub-application registers with the main application, so that the main application has a sub-application registry; wherein the sub-application registry stores a sub-application ID of each sub-application and an application entry of the sub-application;
step 2, the main application manages the whole life cycle of each sub-application, specifically:
step 2.1, the main application comprises a user login module, a layout module, a routing module and a global state sharing module;
step 2.2, when the main application receives user login information through the user login module, obtaining user authority according to the user login information, and pushing menu configuration according to the user authority; the menu configuration comprises sub-application IDs of a plurality of sub-applications which can be combined and are matched with the user authority; then, the main application receives the sub-application IDs of the plurality of sub-applications which need to be combined;
step 2.3, the main application combines a plurality of sub-applications which need to be combined to form a sub-application unit through the layout module;
step 2.4, the main application performs routing configuration on each sub-application through the routing module, including: configuring a path of a browser routing address url and an application entrance of each sub-application;
step 2.5, the main application switches and loads each sub-application by adopting the following mode:
the main application hijacks the browser routing address url, when the browser routing address url changes, the main application is matched with an application inlet of the corresponding sub-application according to the path corresponding to the browser routing address url determined in the step 2.4, and the corresponding sub-application is loaded according to the application inlet;
and 2.6, for the loaded sub-applications, the main application manages the whole life cycle from starting, mounting to destroying.
2. The method for realizing the micro front end based on the multi-application fusion as claimed in claim 1, wherein the step 2.6 specifically comprises:
and exposing related Hook functions in the life cycle change process of the sub-application, and adding additional functions on the corresponding hooks according to different service scenes.
3. The method for implementing the micro front end based on the multi-application fusion as claimed in claim 2, wherein the step 2.6 further comprises:
routing skip is triggered by changing the routing address url of the browser, menu authentication and user identity authentication are carried out in a hook function before the routing skip, and if the token is expired, the browser skips to a login page to log in again;
after the sub-application acquires certain data, the data needs to be used as global shared data, and at this time, a new payload is transferred by using the communication hook, and the global state is synchronously updated.
4. The method according to claim 1, wherein sandbox isolation is used between the sub-applications and the main application, and each sub-application has an independent execution context scope through the sandbox isolation.
5. The method according to claim 1, wherein the main application has a sub-application state monitoring function, a sub-application state updating function and a sub-application state removing monitoring function;
performing state monitoring on each sub-application through the sub-application state monitoring function; when the change of the sub-application state is monitored, updating the state of the sub-application through a sub-application state updating function; and when the sub-application is unloaded, removing the monitoring function through the sub-application state, and moving the sub-application state monitoring function and the sub-application state updating function to complete resource release.
6. The micro front-end implementation method based on multi-application fusion according to claim 1, wherein the global state sharing module is specifically configured to:
the main application stores the sub-application global state of all the sub-applications, and shares the sub-application global state of all the sub-applications to each sub-application through the global state sharing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211604164.6A CN115794093A (en) | 2022-12-13 | 2022-12-13 | Micro front end implementation method based on multi-application fusion |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211604164.6A CN115794093A (en) | 2022-12-13 | 2022-12-13 | Micro front end implementation method based on multi-application fusion |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115794093A true CN115794093A (en) | 2023-03-14 |
Family
ID=85419987
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211604164.6A Pending CN115794093A (en) | 2022-12-13 | 2022-12-13 | Micro front end implementation method based on multi-application fusion |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115794093A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116506215A (en) * | 2023-06-16 | 2023-07-28 | 中国联合网络通信集团有限公司 | Access processing method, device, electronic equipment and storage medium |
| CN116501364A (en) * | 2023-05-05 | 2023-07-28 | 南京领行科技股份有限公司 | Application registration method and device and micro front-end system |
-
2022
- 2022-12-13 CN CN202211604164.6A patent/CN115794093A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116501364A (en) * | 2023-05-05 | 2023-07-28 | 南京领行科技股份有限公司 | Application registration method and device and micro front-end system |
| CN116506215A (en) * | 2023-06-16 | 2023-07-28 | 中国联合网络通信集团有限公司 | Access processing method, device, electronic equipment and storage medium |
| CN116506215B (en) * | 2023-06-16 | 2023-09-12 | 中国联合网络通信集团有限公司 | Access processing method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111737032B (en) | Subprogram running method and device based on microkernel system and electronic equipment | |
| CN115794093A (en) | Micro front end implementation method based on multi-application fusion | |
| US8738589B2 (en) | Classloading technique for an application server that provides dependency enforcement | |
| CN105022630B (en) | A kind of assembly management system and assembly management method | |
| US20230036980A1 (en) | Micro-frontend system, sub-application loading method, electronic device, computer program product, and computer-readable storage medium | |
| CN104714828A (en) | Methods and devices for installing and operating application | |
| US8327341B2 (en) | Integrating aspect oriented programming into the application server | |
| US20070067418A1 (en) | Object oriented web application framework | |
| US20080301637A1 (en) | Profile service based deployment configuration | |
| CN102314358A (en) | Method for deploying conventional applications on cloud platform in SOA (service oriented architecture) way | |
| CN113419710B (en) | Development method and device of applet, electronic equipment and medium | |
| Xu et al. | Caople: A programming language for microservices saas | |
| CN112114890A (en) | Method, device and equipment for processing small program and storage medium | |
| US20130125093A1 (en) | Generating object-oriented programming language code from a multi-domain dynamic simulation model | |
| Banerjee et al. | Programming paradigm and the internet of things | |
| US20080301711A1 (en) | Providing a POJO-based microcontainer for an application server | |
| CN112987936A (en) | Interactive processing method, system, device, equipment and medium | |
| CN115390846A (en) | Compiling construction method and device, electronic equipment and storage medium | |
| CA2928316A1 (en) | Facilitating communication between software components that use middleware | |
| CN112597408A (en) | System fusion method, device, equipment and storage medium | |
| Zneika et al. | Towards a modular and lightweight model for android development platforms | |
| Juneau et al. | Servlets and JavaServer Pages | |
| CN117170738B (en) | Method, system, equipment and storage medium for interaction of Python and Fortran | |
| CN116700745A (en) | Application deployment method and device based on container cloud platform, electronic equipment and medium | |
| CN116088932A (en) | Method, device, equipment and medium for generating application system based on micro-service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |