CN117667028A - Cross-department collaboration system under micro front end architecture - Google Patents
Cross-department collaboration system under micro front end architecture Download PDFInfo
- Publication number
- CN117667028A CN117667028A CN202311658485.9A CN202311658485A CN117667028A CN 117667028 A CN117667028 A CN 117667028A CN 202311658485 A CN202311658485 A CN 202311658485A CN 117667028 A CN117667028 A CN 117667028A
- Authority
- CN
- China
- Prior art keywords
- micro
- root base
- base
- applications
- area
- 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
- 230000006870 function Effects 0.000 claims abstract description 16
- 230000003993 interaction Effects 0.000 claims abstract description 7
- 230000003068 static effect Effects 0.000 claims description 63
- 238000012986 modification Methods 0.000 claims description 6
- 230000004048 modification Effects 0.000 claims description 6
- 238000012552 review Methods 0.000 claims description 6
- 238000012795 verification Methods 0.000 claims description 6
- 238000012545 processing Methods 0.000 claims description 2
- 239000003795 chemical substances by application Substances 0.000 description 9
- 238000000034 method Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a cross-department collaboration system under a micro front end architecture, which meets the flexibility and consistency, provides more working degrees of freedom for a team, and improves the efficiency and collaboration level of the whole ecological system. The technical proposal is as follows: the system comprises a basic root base template, a first regional root base and a second regional root base, wherein the first regional root base is used for loading and coordinating the micro-applications of the region and has the capability of cross-regional access to load the micro-applications of the second region; the second region root base is used for loading and coordinating the micro-applications in the region and has the capability of cross-region access to load the micro-applications in the first region; and the base root base template is used for realizing the unification of interaction and functions between the first area root base and the second area root base, and the first area root base and the second area root base ensure the overall consistency by referring to the base root base templates of the same version.
Description
Technical Field
The invention relates to the field of software engineering, in particular to a cross-department collaboration system under a micro front end architecture.
Background
Micro front-end architecture is a front-end architecture model aimed at splitting large front-end applications into smaller, independently developable and deployable micro-service units, commonly referred to as "micro-applications". These micro applications can be independently developed, maintained and deployed by different teams of departments and then combined together to form a unified front-end application. The goal of the micro front end is to improve maintainability, scalability and team collaboration efficiency of front end development.
Traditional micro front end architectures face a series of challenges in cross-department collaboration. A typical micro-front-end architecture generally includes a root base and a plurality of micro-applications, the root base being responsible for loading and coordinating the individual micro-applications. The root base is the primary container for the entire micro front-end application for loading and coordinating the individual micro applications. The root base itself is a stand-alone front-end application whose main responsibility is to manage and load the individual micro-applications so that they can work together to ultimately form a complete front-end application. In the micro front-end architecture, micro applications refer to a small, stand-alone front-end application unit that can be developed, tested, deployed, and maintained separately. The micro-application is one of the components of the overall micro-front-end application and can be combined together to build a complete front-end application program.
These micro-applications may be developed, maintained, and deployed by separate teams of different departments. However, since the root base is typically responsible for development, maintenance, and deployment by a particular department, this architecture may lead to several problems, depending on the division of responsibilities:
1. difficulty in collaboration: when department B wishes to add a new demand to the root base, it must pass the approval of department a. This may lead to disagreement and thus hamper the implementation of new demands.
2. Code development complexity is high, and responsibility division is unclear: the root base needs to be accessible in both the business and office areas, but the functional requirements of the two areas are different. This is because the root bases of business areas are managed by department a, while the root bases of office areas are managed by department B, and the two departments' requirements for the root bases are not identical. This may lead to the following problems:
(1) The front-end code needs to contain a large amount of judgment logic to distinguish between the different requirements of the two areas, thereby increasing the complexity of the code and affecting the stability of the code on line.
(2) The deployment area of the root base may lead to liability divisions and disputes. For example, when a root base is deployed in a business area, it is developed, maintained, and deployed by department a. However, if the functionality of department B is on-line, department a may claim that it is responsible for department B, which may consider that it was developed by department a and should be undertaken by department a. Please refer to fig. 1 and 2.
At present, there is no comprehensive and mature solution to these needs.
Disclosure of Invention
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
The invention aims to solve the problems, and provides a cross-department collaboration system under a micro front-end architecture, which simultaneously satisfies flexibility and consistency, provides more working degrees of freedom for teams and improves the efficiency and collaboration level of the whole ecological system.
The technical scheme of the invention is as follows: the invention discloses a cross-department collaboration system under a micro front end architecture, which comprises a basic root base template, a first regional root base and a second regional root base, wherein:
the first region root base is used for loading and coordinating the micro-applications in the region and has the capability of cross-region access to load the micro-applications in the second region;
the second region root base is used for loading and coordinating the micro-applications in the region and has the capability of cross-region access to load the micro-applications in the first region;
and the base root base template is used for realizing the unification of interaction and functions between the first area root base and the second area root base, and the first area root base and the second area root base ensure the overall consistency by referring to the base root base templates of the same version.
According to one embodiment of the cross-department collaboration system under the micro front end architecture of the present invention, the first regional root base is a business area root base and the second regional root base is an office area root base.
According to the embodiment of the cross-department collaboration system under the micro front end architecture, the service area root base and the corresponding micro applications are hosted on the same static server, when the service area root base is accessed on a browser client, the browser client sends an Http request to acquire the static resources of the service area root base, the service area root base acquires the static resources of the service area micro applications by using the address of micro application deployment through the Http protocol, and then the service area root base loads the combined micro applications by means of the micro front end framework to finish the display of a front end interface, wherein after the micro applications are deployed to the static server, each micro application is provided with an independent access address, and the service area root base loads the micro applications deployed to the static server through the micro front end framework to realize the dynamic display and the presentation of the interface.
According to the embodiment of the cross-department collaboration system under the micro front end architecture, for the case that the business district base accesses and loads the office district micro-application in a cross-region mode, the micro-application of the office district is hosted on another static server, an agent is configured on the static server where the business district base is located, the business district base initiates a request for the micro-application of the office district through the agent, and the request is forwarded to the static server of the office district through the agent server, so that the business district base can be ensured to load and coordinate the micro-application of the office district smoothly.
According to the embodiment of the cross-department collaboration system under the micro front end architecture, the office area root base and the corresponding micro applications are hosted on the same static server, when the office area root base is accessed on a browser client, the browser client sends an Http request to acquire static resources of the office area root base, the office area root base acquires static resources of the office area micro applications by using an Http protocol through addresses deployed by the micro applications, and then the office area root base loads combined micro applications by means of a micro front end framework to finish the display of a front end interface, wherein after the micro applications are deployed to the static server, each micro application is enabled to have an independent access address, and the office area root base loads the micro applications deployed to the static server through the micro front end framework to realize the dynamic display and the presentation of the interface.
According to the embodiment of the cross-department collaboration system under the micro front end architecture, for the case that the office area root base accesses and loads the business area micro application in a cross-region mode, the business area micro application is hosted on another static server, an agent is configured on the static server where the office area root base is located, the office area root base initiates a request for the business area micro application through the agent, and the request is forwarded to the business area static server through the agent server, so that the office area root base can be ensured to load and coordinate the business area micro application smoothly.
According to an embodiment of the cross-department collaboration system under the micro front end architecture of the present invention, the base root base template is further configured with a function of modification and change, the function comprising the following processing steps: the base root base template code is firstly subjected to code review and verification after modification, version release can be carried out after the review verification is passed, and after version release, the business root base updates the version of the base root base template, and meanwhile, the office root base also updates the version of the base root base template.
According to one embodiment of the cross-department collaboration system under the micro front end architecture of the present invention, multiple custom options with flexibility are introduced into the base root base template, which allow individual regions to be adjusted according to their specific needs.
According to an embodiment of the cross-department collaboration system under the micro front end architecture of the present invention, the customization options include interface elements and function modules.
Compared with the prior art, the invention has the following beneficial effects: on the one hand, the invention realizes the diversification of the root bases, and the traditional micro front end architecture usually only comprises one root base, so that the flexibility in the software development process is limited. The invention adopts a revolutionary improvement, splits the root base into two independent applications (the business area root base and the office area root base), breaks through the traditional single root base paradigm, provides a greater degree of freedom for a software development team, and makes the cross-department collaboration easier. In order to ensure the consistency of user experience, a basic root base template is introduced, and is used as a framework to provide a common style theme for the service area root base and the office area root base, which means that users can enjoy the same look and feel whether the users are in the service area or the office area. At the same time, this template also helps to maintain consistency of style, whether between different departments or between different applications.
Drawings
The above features and advantages of the present invention will be better understood after reading the detailed description of embodiments of the present disclosure in conjunction with the following drawings. In the drawings, the components are not necessarily to scale and components having similar related features or characteristics may have the same or similar reference numerals.
Fig. 1 shows a schematic diagram of a root base deployed in a service area.
Fig. 2 shows a schematic diagram of a root base deployed in an office area.
Fig. 3 shows a schematic diagram of a cross-department collaboration system under a micro front end architecture of the present invention.
Fig. 4 illustrates a schematic diagram of service area root base access loading micro-applications in the system illustrated in fig. 3.
FIG. 5 illustrates a flow chart of a modified variation of the base root base template in the system illustrated in FIG. 3.
Detailed Description
The invention is described in detail below with reference to the drawings and the specific embodiments. It is noted that the aspects described below in connection with the drawings and the specific embodiments are merely exemplary and should not be construed as limiting the scope of the invention in any way.
Fig. 3 illustrates the principle of the cross-department collaboration system under the micro front end architecture of the present invention. Referring to fig. 3, the system of the present embodiment includes: a base root base template, a first regional root base (in this embodiment, a business zone root base), and a second regional root base (in this embodiment, an office zone root base). Compared with the prior art, the invention splits the original single root base application into two independent applications: business zone root base and office zone root base. The service area root base is used for loading and coordinating the micro-applications in the local area (namely the service area), and has the capability of cross-regional access to load the micro-applications in the office area. The office area root base is used for loading and coordinating the micro-applications in the local area (namely the office area), and has the capability of cross-regional access to load the business area micro-applications. The basic root base template is used for realizing the unification of interaction and functions between the service area root base and the office area root base. The business area root base and the office area root base ensure the overall consistency by referring to the base root base templates of the same version.
A service area is a specific area for deployment of online applications. In this area, the front-end application is hosted on a dedicated static server that is deployed in a portion of the service area where the back-end application associated with the service is deployed. An office area is a specific area for deployment of online applications. In this area, the front-end application is hosted on a dedicated static server that is deployed in a portion of the office area where office-related back-end applications are deployed. The cross-regional access is that an application of a service region accesses an application of an office region, or that an application of an office region accesses an application of a service region, and this access mode is called cross-regional access. In practice, cross-regional access involves data interactions between two separate static servers. Under the micro front-end architecture, cross-regional access becomes a key collaboration mechanism, as the micro applications of the business and office areas may be hosted on different static servers, respectively. In general, to achieve cross-regional access, the service area root base and the office area root base employ proxy configuration techniques to ensure efficient and reliable data transfer between two static servers.
The service area root base is used for loading and coordinating the micro-applications in the area and has the capability of cross-area access to load the micro-applications in the office area. Referring specifically to fig. 4, the service area root base and the micro application in this embodiment are both single page applications, which are hosted on the same static server (e.g., the service area static server shown in fig. 4). In this embodiment, the static server is a server for providing static files (e.g., HTML, CSS, javaScript, images, etc.). Static servers are typically used to host static websites or Single Page Applications (SPAs), where all pages and resources are static and do not need to be generated on the server in real time. A user may access a static server through the Http protocol to obtain static resources hosted thereon. The acquisition mode initiates a request through a browser or other Http clients, and the server responds and transmits corresponding files, so that simple and efficient resource delivery is realized.
When the service area root base is accessed on the browser client, the browser client sends an Http request to acquire the static resources of the service area root base, and the service area root base acquires the static resources of the service area micro-application by utilizing the Http protocol through the address of the micro-application deployment. And then, loading the combined micro-application by the service area root base by means of the micro-front end framework to finish the display of the front end interface, specifically, after the micro-application is deployed to the static server, each micro-application is enabled to have an independent access address, and the root base loads the micro-application deployed to the static server through the micro-front end framework to realize the dynamic display and the presentation of the interface.
For the case of cross-regional access loading of the office micro-application, because the office micro-application is hosted on another static server (such as the office static server shown in fig. 4), in order to implement cross-regional communication between the business area root base and the office micro-application, in this embodiment, an agent is configured on the static server where the business area root base is located. Through the proxy, the service area root base can initiate a request for the office area micro-application and forward the request to the office area static server through the proxy server so as to establish a reliable communication bridge, and ensure that the service area root base can smoothly load and coordinate the office area micro-application. Where resource access between static servers may typically be achieved through agents. The proxy acts as an intermediary, forwarding resource requests on one static server to another, and returning responses to the requesting party. This approach allows the static servers to cooperate with each other, sharing resources, while maintaining a compact client request and response flow. In one application example, the static server employed is Apache, and the proxy function is also provided by Apache.
The office root base can also load the micro-applications of the area and support cross-area access to the business area micro-applications. The principle is similar to the implementation method of the service area root base shown in fig. 4.
When the office area root base is accessed on a browser client, the browser client sends an Http request to acquire static resources of the office area root base, the office area root base acquires the static resources of the office area micro-application by using an address deployed by the micro-application through an Http protocol, and then the office area root base loads the combined micro-application by using a micro-front-end frame to finish the display of a front-end interface, wherein after the micro-application is deployed to the static server, each micro-application is enabled to have an independent access address, and the office area root base loads the micro-application deployed to the static server through the micro-front-end frame to realize the dynamic display and the presentation of the interface.
By proxy configuration, the office root base implements cross-regional communication with the business region micro-applications. The architecture design of the bidirectional intercommunication successfully eliminates barriers between business and office areas and provides greater collaboration flexibility for different departments. By skillfully configuring the agent on the static server, the business zone root base and the office zone root base can seamlessly realize cross-regional access, and an efficient and reliable solution is provided for department collaboration under the micro-front-end architecture.
The root base is split into two independent root bases. However, this split may cause inconsistency problems in interactions, user experience, and functional implementation. The basic root base template in the system of the embodiment is used for realizing the unification of interaction and functions between the service area root base and the office area root base. The business area root base and the office area root base ensure the consistency of the whole by referring to templates of the same version. As shown in fig. 5, the flow of modification and change of the base root template is shown.
As shown in fig. 5, the base root base template code is firstly subjected to code review and verification after modification, and can be released after the review and verification are passed, and after the release of the version, the service area root base updates the version of the base root base template, and the office area root base also updates the version of the base root base template.
Although the business zone root base and office zone root base use the same base root base template, the present invention is also able to introduce flexible customization options in the base root base template. These customization options allow the various regions to be tailored to their specific needs, including configurable interface elements (e.g., buttons, icons, etc.), functional modules (e.g., modules needed for a particular business). By providing these customization options, the individual unique needs can be met on the basis of ensuring overall consistency of the root bases of the two regions, thereby providing a more flexible and personalized user experience. Meanwhile, from the development point of view, the service area root base and the office area root base are two independent applications, have different functions and customization options, and the balance enables different departments to work cooperatively better and provides more flexible application deployment and maintenance modes.
While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more embodiments, occur in different orders and/or concurrently with other acts from that shown and described herein or not shown and described herein, as would be understood and appreciated by those skilled in the art.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disk) and disc (disk) as used herein include Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disk) usually reproduce data magnetically, while discs (disk) reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. A cross-department collaboration system under a micro front end architecture, the system comprising a base root template, a first regional root base, a second regional root base, wherein:
the first region root base is used for loading and coordinating the micro-applications in the region and has the capability of cross-region access to load the micro-applications in the second region;
the second region root base is used for loading and coordinating the micro-applications in the region and has the capability of cross-region access to load the micro-applications in the first region;
and the base root base template is used for realizing the unification of interaction and functions between the first area root base and the second area root base, and the first area root base and the second area root base ensure the overall consistency by referring to the base root base templates of the same version.
2. The cross-department collaboration system under the micro front end architecture of claim 1, wherein the first regional root base is a business region root base and the second regional root base is an office region root base.
3. The cross-department collaboration system under the micro front end architecture according to claim 2, wherein the service area root base and the corresponding micro applications are hosted on the same static server, when the service area root base is accessed on a browser client, the browser client sends an Http request to obtain static resources of the service area root base, the service area root base obtains the static resources of the service area micro applications by using an address deployed by the micro applications through an Http protocol, and then the service area root base loads the combined micro applications by means of a micro front end framework to complete the display of a front end interface, wherein after the micro applications are deployed to the static server, each micro application is provided with an independent access address, and the service area root base loads the micro applications deployed to the static server through the micro front end framework to realize the dynamic display and the presentation of the interface.
4. The cross-department collaboration system under the micro front end architecture of claim 2, wherein for the case of cross-regional access of the business area base to load the office area micro-applications, the office area micro-applications are hosted on another static server, an agent is configured on the static server where the business area base is located, the business area base initiates a request for the office area micro-applications through the agent, and the request is forwarded to the office area static server through the agent server, so that smooth loading and coordination of the business area base with the office area micro-applications are ensured.
5. The cross-department collaboration system under the micro front end architecture according to claim 2, wherein the office area root base and the corresponding micro applications are hosted on the same static server, when the office area root base is accessed on a browser client, the browser client sends an Http request to obtain static resources of the office area root base, the office area root base obtains static resources of the office area micro applications by using an address deployed by the micro applications through an Http protocol, and then the office area root base loads combined micro applications by means of a micro front end framework to complete display of a front end interface, wherein after the micro applications are deployed to the static server, each micro application is provided with an independent access address, and the office area root base loads the micro applications deployed to the static server through the micro front end framework to realize dynamic display and presentation of the interface.
6. The cross-department collaboration system under the micro front end architecture of claim 2, wherein for the case of cross-regional access of the office area root base to load the business area micro-applications, the business area micro-applications are hosted on another static server, an agent is configured on the static server where the office area root base is located, the office area root base initiates a request for the business area micro-applications through the agent, and the request is forwarded to the business area static server through the agent server, so that smooth loading and coordination of the business area micro-applications by the office area root base are ensured.
7. The cross-department collaboration system under the micro front end architecture of claim 2, wherein the base root base template is further configured with a function of modifying changes, the function comprising the processing steps of: the base root base template code is firstly subjected to code review and verification after modification, version release can be carried out after the review verification is passed, and after version release, the business root base updates the version of the base root base template, and meanwhile, the office root base also updates the version of the base root base template.
8. The cross-department collaboration system under the micro front end architecture of claim 2, wherein a plurality of custom options with flexibility are introduced into the base root base template, the custom options allowing individual regions to be tailored to their specific needs.
9. The cross-department collaboration system under the micro front end architecture of claim 8, wherein the customization options include interface elements and function blocks.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311658485.9A CN117667028A (en) | 2023-12-05 | 2023-12-05 | Cross-department collaboration system under micro front end architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311658485.9A CN117667028A (en) | 2023-12-05 | 2023-12-05 | Cross-department collaboration system under micro front end architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117667028A true CN117667028A (en) | 2024-03-08 |
Family
ID=90067667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311658485.9A Pending CN117667028A (en) | 2023-12-05 | 2023-12-05 | Cross-department collaboration system under micro front end architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117667028A (en) |
-
2023
- 2023-12-05 CN CN202311658485.9A patent/CN117667028A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11184427B2 (en) | Local microservice development for remote deployment | |
| Chappell | Introducing the Azure services platform | |
| US10574644B2 (en) | Stateful session manager | |
| CN104823189B (en) | Frame is allocated for connect equipment | |
| Harty | Implementing innovation: designers, users and actor-networks | |
| EP2279602B1 (en) | Systems and methods for remoting multimedia plugin calls | |
| US20110078333A1 (en) | Synchronization of server-side cookies with client-side cookies | |
| US11165585B2 (en) | Token repository and integration | |
| Andrawos et al. | Cloud Native Programming with Golang: Develop microservice-based high performance web apps for the cloud with Go | |
| CN109343934A (en) | A kind of private based on container takes framework and its builds and method for visualizing | |
| CN109565443A (en) | Certificate deployment based on range | |
| Heikkinen et al. | Tandem browsing toolkit: Distributed multi-display interfaces with web technologies | |
| Buell et al. | From dreamweaver to Drupal: A University Library website case study | |
| CN117667028A (en) | Cross-department collaboration system under micro front end architecture | |
| Ludwig et al. | REST-based management of loosely coupled services | |
| US7818713B2 (en) | Method, system and program product for generating requirement relationships for designing a solution | |
| Bartlett | Building Scalable PHP Web Applications Using the Cloud: A Simple Guide to Programming and Administering Cloud-Based Applications | |
| CN104471541A (en) | Hybrid application environments | |
| Banerjee | A systematic study on the development of decentralized application (dApp) | |
| MVP et al. | Microsoft System Center 2012 R2 Operations Manager Cookbook | |
| Penberthy | Exam Ref 70-486 Developing ASP. NET MVC 4 Web Applications (MCSD): Developing ASP. NET MVC 4 Web Applications | |
| TWI735151B (en) | Methods of providing services using official accounts of communication software | |
| Asselin et al. | VMware Horizon Suite: Building End User Services | |
| US11829741B2 (en) | Instantiated deployment of microservices | |
| Bhatt | Liferay Portal performance best practices |
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 |