CN111008015B - Micro front-end application framework based on front-end technology - Google Patents
Micro front-end application framework based on front-end technology Download PDFInfo
- Publication number
- CN111008015B CN111008015B CN201911153566.7A CN201911153566A CN111008015B CN 111008015 B CN111008015 B CN 111008015B CN 201911153566 A CN201911153566 A CN 201911153566A CN 111008015 B CN111008015 B CN 111008015B
- Authority
- CN
- China
- Prior art keywords
- end application
- micro front
- micro
- business
- application
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention relates to a micro front-end application frame realized based on a front-end technology, which is characterized by comprising the following components: general micro front end application and business micro front end application; the micro front-end application framework realized based on the front-end technology is used for enabling the universal micro front-end application and the business micro front-end application to be in seamless connection; the standard interface for the generic micro front-end application and the business micro front-end application includes the following fields: code, name, icon, connection, js code, style code. The following functions can be realized: the user changes the requirements of the business process and business logic at the interface level; business cooperation requirements between applications; frequently adding new service, and seamlessly integrating with the existing service module; dynamic updating of the local application module (development and deployment may be performed independently); tenant application configuration real-time modification updates.
Description
Technical Field
The embodiment of the invention relates to the technical field of computer information, in particular to a micro front-end application framework realized based on a front-end technology.
Background
SaaS (Software-as-a-Service) is a completely innovative Software application mode that starts to rise in the 21 st century with the development of internet technology and the maturation of application Software. In an application scenario mainly comprising SaaS, application development is gradually inclined towards the front end, and the demands of customers on quick update, iteration and quick integration of new services are more and more urgent, especially on enterprises, government and other institutions, the demands on personalized customization of service systems and update frequency are higher, however, the demands have conflict with SaaS productization solutions.
In order to cope with the above-mentioned demands, in the related art, most of the code frames based on development, such as practice, reduce, belong to only the technical frames, have a certain learning curve cost, and require a certain period for building the system. In addition, front-end components are provided, but most of the front-end components are biased towards UI front-end components, so that little convenience is provided for developers on the basis of a pure technical framework, and the application cannot be quickly built. Furthermore, the front-end component may also provide configuration of certain programs, but lacks the user to make a small number of application interface configurations at the product level.
Disclosure of Invention
In view of the above, in order to solve the above technical problems or part of the technical problems, an embodiment of the present invention provides a micro front-end application framework implemented based on a front-end technology.
The embodiment of the invention provides a micro front-end application framework based on a front-end technology, which comprises the following components: general micro front end application and business micro front end application;
the micro front-end application framework realized based on the front-end technology is used for enabling the universal micro front-end application and the business micro front-end application to be in seamless connection;
the standard interface for the generic micro front-end application and the business micro front-end application includes the following fields: code, name, icon, connection, js code, style code.
In one possible implementation manner, the standard interfaces of the general micro front end application and the business micro front end application are realized by the following ways:
the standard interface of the general micro front-end application and the business micro front-end application adopts a restful-style HTTP protocol interface.
In one possible embodiment, the generic micro front-end application comprises:
an event message module, a front end workflow module, a configuration engine module, a design time module, and a runtime module.
In one possible implementation, the runtime module includes the following APIs:
the method comprises the steps of initializing a general micro front-end application, and finishing login of the general micro front-end application and loading of related resources;
the second API acquires the universal micro front-end application code so as to acquire the detailed information of the universal micro front-end application;
the third API obtains detailed configuration of the universal micro front-end application according to the universal micro front-end application code;
a fourth API, according to the general micro front end application code, obtaining the general micro front end application module configuration;
a fifth API supporting general micro front end application debug mode switching;
a sixth API for supporting the switching of the general micro front end application log mode;
and seventh API, obtaining the event supported by the general micro front-end application.
In one possible implementation, the design-time module is an edit configuration page of the runtime module for configuring configuration parameters of a generic micro-front-end application.
In one possible implementation, the front-end workflow module is implemented by:
a section of simple business logic is customized, compiled and updated in a script-like manner, so that subsequent expansion and updating are facilitated.
In one possible implementation, the basic protocol of the event message module communication includes the following fields:
the message transmission includes the following fields: message Id, message name, app code, message body, message level.
In one possible implementation, the configuration engine module is implemented by:
the general configuration is configured by a group of configuration paths aiming at a configuration unit, and the configuration value can be any Json data;
the type value of the configuration unit comprises: tenant/application system/module/user/component, and support custom extension;
the configuration path is composed of a series of ordered key-value pairs, and the matching rule is to match the preamble path item preferentially;
each path item of the configuration path may use a wild card "×" to indicate that all values are matched.
In one possible implementation, the service micro front-end application includes the following states:
development/testing: the business micro front-end application in the developing/testing process of the developer is only visible to the current developer and cannot be issued;
registration state: the registered business micro front-end application is visible only to the current tenant manager, and the current tenant can perform personalized parameter configuration on the business micro front-end application;
release state: the published business micro front-end application is visible in an application list, a subscriber can subscribe the business micro front-end application, is visible in an application Portal of a tenant authorized to subscribe, and can use and personally configure the business micro front-end application;
frozen state: the frozen business micro front-end application can only be seen in Portal, but all business functions are not available to all subscribers.
In one possible implementation manner, the micro front end application framework implemented based on the front end technology further includes:
adding/registering a general micro front end application and a business micro front end application, configuring a general micro front end application and a business micro front end application, issuing a general micro front end application and a business micro front end application, deleting a general micro front end application and a business micro front end application.
The micro front-end application framework based on the front-end technology provided by the embodiment of the invention can realize the following functions: the user changes the requirements of the business process and business logic at the interface level; business cooperation requirements between applications; frequently adding new service, and seamlessly integrating with the existing service module; dynamic updating of the local application module (development and deployment may be performed independently); tenant application configuration real-time modification updates.
Drawings
In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present description, and other drawings may be obtained according to these drawings for a person having ordinary skill in the art.
FIG. 1 is a schematic diagram of a micro-front-end application framework implemented based on front-end technology, according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a general micro front end application according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a lifecycle of a business micro front-end application according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a service micro front end application state according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of managing a generic micro front-end application and a business micro front-end application according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of a configuration generic micro front-end application and a business micro front-end application according to an embodiment of the present invention;
fig. 7 is a schematic diagram of configuration of general micro front-end applications and thematic information of business micro front-end applications according to an embodiment of the invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
For the purpose of facilitating an understanding of the embodiments of the present invention, reference will now be made to the following description of specific embodiments, taken in conjunction with the accompanying drawings, which are not intended to limit the embodiments of the invention.
As shown in fig. 1, a schematic diagram of a micro front-end application framework implemented based on a front-end technology according to an embodiment of the present invention may accommodate a general micro front-end application and a business micro front-end application.
The micro front-end application framework realized based on the front-end technology can enable the universal micro front-end application and the business micro front-end application to be in seamless connection, and simultaneously support registration of the universal micro front-end application and the business micro front-end application, thereby being convenient for rapid integration.
For general micro front-end application, the method can comprise two three-dimensional map engines, inter-application event communication, layout management, front-end data model management, real-time message notification, front-end workflow [ the front-end application which is defined in advance executes a circulation logic flow ], application configuration distribution update management, unified login authentication management and unified service call management;
for business micro-front-end applications, such as business thematic pages, user organization architecture management, rights management, workflow management may be included.
In addition, the micro front-end application framework realized based on the front-end technology can support multi-tenant management, different tenants can see different general micro front-end applications and business micro front-end applications, and the general micro front-end applications and the business micro front-end applications are customized.
In the embodiment of the invention, for the general micro front-end application and the business micro front-end application, the adopted standard interface comprises the following fields: codes, names, icons, connections, js codes, style codes, as shown in table 1 below.
TABLE 1
The standard interface for acquiring the general micro front-end application and the related information of the business micro front-end application adopts a HTTP protocol interface in a restful style, and the related information of the app can be returned according to the app code.
For general purpose micro front end applications, as shown in fig. 2, the following modules are included: an event message module, a front end workflow module, a configuration engine module, a design time module, and a runtime module.
For the runtime module, a standard set of APIs (Application Programming Interface, application program interface) is provided:
the method comprises the steps of initializing a general micro front-end application, completing login of the general micro front-end application and loading of related resources (codes, style files and the like) by a first API;
the second API acquires the universal micro front-end application code so as to acquire the detailed information of the universal micro front-end application;
the third API obtains detailed configuration of the universal micro front-end application according to the universal micro front-end application code;
a fourth API, according to the general micro front end application code, obtaining the general micro front end application module configuration;
a fifth API supporting general micro front end application debug mode switching;
a sixth API for supporting the switching of the general micro front end application log mode;
and seventh API, obtaining the event supported by the general micro front-end application.
For the design-time module, the editing configuration page of the runtime module can be performed in a System and an application (performed according to a tenant unit), and configuration parameters of the general micro front-end application, a name, a basic mode and script(s) in the front-end workflow module are configured.
And for the front-end workflow module, a section of simple business logic is customized, compiled and updated in a script-like manner, so that the follow-up expansion and updating are facilitated. The script must be editable by the user, and is executed when the tenant configures the system Application, application Micro Application component.
For event message modules, the hops between application pages are served, or the execution of the business driven flow may be message driven, and the source of the driving may be the front end workflow module. The basic protocol of its communication is as follows:
1. the message transmission needs to contain the following fields: the message transmission includes the following fields: message Id, message name, app code, message body, message level;
2. message acceptance may be subscribed to through a subscore interface: optionally, subscriptions may be made based on the message ID.
For a core point of the micro front-end application framework realized based on the front-end technology, personalized customization is quickly supported, so that the following principle is realized for a configuration engine module:
the general configuration is configured by a set of configuration paths (routing) for a configuration unit (unit), and the configuration value may be any Json data.
Wherein: the type (unit_type) value of the configuration unit includes: tenant (tenant)/application system (app)/module (app_module)/user/component (widget) and supports custom extensions;
the configuration path (routing) consists of a series of ordered key-value pairs, and the matching rule will preferentially match the preamble path item;
each path entry of the configuration path (routing) may use a wildcard "×to indicate that all values are matched;
the personalized system general configuration service adopts a unified configuration parameter storage and access interface, stores data by using a Redis database, and starts persistence.
The basic design goal of the personalized system general configuration service is to use the personalized configuration values when the personalized configuration exists and to adopt the general configuration values when the personalized configuration does not exist for the configuration under various scenes. For example, the component interface color of one weather environment adopts a blue background, the tenant T1 hopes to use a red background, the tenant T1 can configure the personalized configuration for the T1, the configuration only effectively uses the red background for the T1, other tenants are not affected by the setting of the T1 tenant, the tenant T2 does not configure personalized parameters, and the general configuration is adopted when the T2 accesses the system, namely, the blue background is adopted.
For the service micro front-end application, as shown in fig. 3, for the life cycle of the service micro front-end application, the following states exist for the service micro front-end application, as shown in fig. 4:
development/testing: the business micro front-end application in the developing/testing process of the developer is only visible to the current developer and cannot be issued;
registration state: the registered business micro front-end application is visible only to the current tenant manager, and the current tenant can perform personalized parameter configuration on the business micro front-end application;
release state: the published business micro front-end application is visible in an application list, a subscriber can subscribe the business micro front-end application, is visible in an application Portal of a tenant authorized to subscribe, and can use and personally configure the business micro front-end application;
frozen state: the frozen business micro front-end application can only be seen in Portal, but all business functions are not available to all subscribers.
In addition, in the micro front-end application framework realized based on the front-end technology, unified management of the general micro front-end application and the business micro front-end application can be realized, including: adding/registering a general micro front end application and a business micro front end application, configuring a general micro front end application and a business micro front end application, publishing a general micro front end application and a business micro front end application, deleting a general micro front end application and a business micro front end application are shown in fig. 5.
For configuring the general micro front-end application and the business micro front-end application, the basic information, the global configuration information, the thematic information and the menu of the general micro front-end application and the business micro front-end application are configured, as shown in fig. 6.
For the configuration of the general micro front-end application and the thematic information of the business micro front-end application, the layout of the general micro front-end application and the business micro front-end application and the functional business component parameters contained in the page are configured, as shown in fig. 7.
Through the description of the micro front-end application framework based on the front-end technology provided by the embodiment of the invention, the following functions can be realized: the user changes the requirements of the business process and business logic at the interface level; business cooperation requirements between applications; frequently adding new service, and seamlessly integrating with the existing service module; dynamic updating of the local application module (development and deployment may be performed independently); tenant application configuration real-time modification updates.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of function in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. 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 steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (9)
1. The micro front-end application system based on the front-end technology is characterized by comprising:
general micro front end application and business micro front end application; the micro front-end application system realized based on the front-end technology is used for enabling the universal micro front-end application and the business micro front-end application to be in seamless connection;
the standard interface for the generic micro front-end application and the business micro front-end application includes the following fields: coding, name, icon, connection, js code, style code;
the general micro front-end application comprises a runtime module;
wherein the runtime module comprises the following APIs:
the method comprises the steps of initializing a general micro front-end application, and finishing login of the general micro front-end application and loading of related resources;
the second API acquires the universal micro front-end application code so as to acquire the detailed information of the universal micro front-end application;
the third API obtains detailed configuration of the universal micro front-end application according to the universal micro front-end application code;
a fourth API, according to the general micro front end application code, obtaining the general micro front end application module configuration;
a fifth API supporting general micro front end application debug mode switching;
a sixth API for supporting the switching of the general micro front end application log mode;
and seventh API, obtaining the event supported by the general micro front-end application.
2. The micro front-end application system implemented based on front-end technology according to claim 1, wherein the standard interfaces of the general micro front-end application and the business micro front-end application are implemented by the following ways:
the standard interface of the general micro front-end application and the business micro front-end application adopts a restful-style HTTP protocol interface.
3. The front-end technology implementation based micro front-end application system of claim 1, wherein the generic micro front-end application further comprises:
the system comprises an event message module, a front-end workflow module, a configuration engine module and a design time module.
4. The micro front-end application system implemented based on front-end technology according to claim 3, wherein the design-time module is an edit configuration page of the runtime module for configuring configuration parameters of a general purpose micro front-end application.
5. The micro front-end application system implemented based on front-end technology according to claim 1, wherein the front-end workflow module is implemented by:
a section of simple business logic is customized, compiled and updated in a script-like manner, so that subsequent expansion and updating are facilitated.
6. The micro front-end application system implemented based on front-end technology of claim 1, wherein the basic protocol of the event message module communication comprises the following fields:
the message transmission includes the following fields: message Id, message name, app code, message body, message level.
7. The micro front-end application system implemented based on front-end technology of claim 1, wherein the configuration engine module is implemented by:
the general configuration is configured by a group of configuration paths aiming at a configuration unit, and the configuration value can be any Json data;
the type value of the configuration unit comprises: tenant/application system/module/user/component, and support custom extension;
the configuration path is composed of a series of ordered key-value pairs, and the matching rule is to match the preamble path item preferentially;
each path item of the configuration path may use a wild card "×" to indicate that all values are matched.
8. The micro front-end application system implemented based on front-end technology according to claim 1, wherein the business micro front-end application comprises the following states:
development/testing: the business micro front-end application in the developing/testing process of the developer is only visible to the current developer and cannot be issued;
registration state: the registered business micro front-end application is visible only to the current tenant manager, and the current tenant can perform personalized parameter configuration on the business micro front-end application;
release state: the published business micro front-end application is visible in an application list, a subscriber can subscribe the business micro front-end application, is visible in an application Portal of a tenant authorized to subscribe, and can use and personally configure the business micro front-end application;
frozen state: the frozen business micro front-end application can only be seen in Portal, but all business functions are not available to all subscribers.
9. The front-end technology based micro front-end application system of claim 1, further comprising:
adding/registering a general micro front end application and a business micro front end application, configuring a general micro front end application and a business micro front end application, issuing a general micro front end application and a business micro front end application, deleting a general micro front end application and a business micro front end application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911153566.7A CN111008015B (en) | 2019-11-22 | 2019-11-22 | Micro front-end application framework based on front-end technology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911153566.7A CN111008015B (en) | 2019-11-22 | 2019-11-22 | Micro front-end application framework based on front-end technology |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111008015A CN111008015A (en) | 2020-04-14 |
| CN111008015B true CN111008015B (en) | 2023-07-04 |
Family
ID=70113091
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911153566.7A Active CN111008015B (en) | 2019-11-22 | 2019-11-22 | Micro front-end application framework based on front-end technology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008015B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112015411B (en) * | 2020-08-14 | 2021-04-20 | 深圳市卓智荟教育科技有限公司 | Education application interface configuration method and device based on SAAS and readable storage medium |
| CN112612467A (en) * | 2020-12-22 | 2021-04-06 | 中国建设银行股份有限公司 | Method and device for processing micro front-end architecture based on qiankun |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609271A (en) * | 2012-02-20 | 2012-07-25 | 山东大学 | Metadata-driven visual SaaS (Software as a Service) application customizing method and metadata-driven visual SaaS application customizing system |
| CN102937901A (en) * | 2012-10-17 | 2013-02-20 | 武汉钢铁(集团)公司 | Multi-tenant architecture design method |
| CN105068794A (en) * | 2015-07-17 | 2015-11-18 | 浪潮软件股份有限公司 | Realization method for supporting local research and development of Web page |
| CN105630472A (en) * | 2014-11-03 | 2016-06-01 | 中国科学院沈阳自动化研究所 | Quick client development frame for manufacturing execution system and software development method for frame |
| CN106293863A (en) * | 2016-07-26 | 2017-01-04 | 北京北森云计算股份有限公司 | The compiling of multilingual cloud realizes the method and system that systemic-function dynamic expansion is replaced |
| CN107193546A (en) * | 2017-04-11 | 2017-09-22 | 国网天津市电力公司信息通信公司 | A kind of micro services business application system |
| CN108052318A (en) * | 2018-01-03 | 2018-05-18 | 上海火杉信息科技有限公司 | It is a kind of that collaborative platform is knitted based on the multigroup of SaaS patterns |
| CN108322471A (en) * | 2016-05-11 | 2018-07-24 | 甲骨文国际公司 | Multi-tenant identity and data security management cloud service |
| CN109783083A (en) * | 2019-01-16 | 2019-05-21 | 福建天泉教育科技有限公司 | WEB application development approach and its system |
| CN110083341A (en) * | 2019-04-19 | 2019-08-02 | 上海上湖信息技术有限公司 | A kind of front end development platform, front end development approach and page display method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9043458B2 (en) * | 2013-03-19 | 2015-05-26 | Cognizant Technology Solutions India Pvt. Ltd. | Framework for facilitating implementation of multi-tenant SaaS architecture |
| US10564951B2 (en) * | 2016-02-26 | 2020-02-18 | Dell Products L.P. | Managed software as a service deployment utilizing a client key to generate a one-time use reference for delivery |
-
2019
- 2019-11-22 CN CN201911153566.7A patent/CN111008015B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609271A (en) * | 2012-02-20 | 2012-07-25 | 山东大学 | Metadata-driven visual SaaS (Software as a Service) application customizing method and metadata-driven visual SaaS application customizing system |
| CN102937901A (en) * | 2012-10-17 | 2013-02-20 | 武汉钢铁(集团)公司 | Multi-tenant architecture design method |
| CN105630472A (en) * | 2014-11-03 | 2016-06-01 | 中国科学院沈阳自动化研究所 | Quick client development frame for manufacturing execution system and software development method for frame |
| CN105068794A (en) * | 2015-07-17 | 2015-11-18 | 浪潮软件股份有限公司 | Realization method for supporting local research and development of Web page |
| CN108322471A (en) * | 2016-05-11 | 2018-07-24 | 甲骨文国际公司 | Multi-tenant identity and data security management cloud service |
| CN106293863A (en) * | 2016-07-26 | 2017-01-04 | 北京北森云计算股份有限公司 | The compiling of multilingual cloud realizes the method and system that systemic-function dynamic expansion is replaced |
| CN107193546A (en) * | 2017-04-11 | 2017-09-22 | 国网天津市电力公司信息通信公司 | A kind of micro services business application system |
| CN108052318A (en) * | 2018-01-03 | 2018-05-18 | 上海火杉信息科技有限公司 | It is a kind of that collaborative platform is knitted based on the multigroup of SaaS patterns |
| CN109783083A (en) * | 2019-01-16 | 2019-05-21 | 福建天泉教育科技有限公司 | WEB application development approach and its system |
| CN110083341A (en) * | 2019-04-19 | 2019-08-02 | 上海上湖信息技术有限公司 | A kind of front end development platform, front end development approach and page display method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111008015A (en) | 2020-04-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107979508B (en) | Micro-service test method and device | |
| US10983774B2 (en) | Extensions for deployment patterns | |
| US8645945B2 (en) | Method and apparatus for dynamic middleware assembly | |
| CN103077024B (en) | A kind of device and method supporting the on-demand customization of SaaS application flow and operation | |
| US10996997B2 (en) | API-based service command invocation | |
| US10055393B2 (en) | Distributed version control of orchestration templates | |
| CN107203465B (en) | System interface testing method and device | |
| US20190327322A1 (en) | Design theme-based push notifications | |
| CN108279882B (en) | Framework generation method, device, equipment and computer readable medium | |
| CN111008015B (en) | Micro front-end application framework based on front-end technology | |
| US20220214931A1 (en) | System and method for exposing features of integration platform adapters as first-class actions in an orchestration template | |
| CN107193565B (en) | Method for developing native APP (application) across mobile terminals | |
| US11909640B2 (en) | Creating endpoints | |
| CN113434063B (en) | Information display method, device and equipment | |
| CN112068879A (en) | Method and device for constructing client application development framework based on configuration | |
| CN109933355B (en) | Application program upgrading method and device | |
| CN111124523A (en) | Method and apparatus for initializing applications | |
| CN115167822A (en) | Branch code merging method, device, equipment and storage medium | |
| CN110377367B (en) | Component configuration method and device, electronic terminal and computer readable storage medium | |
| KR20170020366A (en) | Subscriber defined dynamic eventing | |
| CN113050962A (en) | Mobile service upgrading method, device and terminal | |
| US20240070146A1 (en) | Database systems and methods of batching data requests for application extensions | |
| US20240069933A1 (en) | Database systems and client-side field retrieval methods | |
| US20240070149A1 (en) | Database systems and client-side data synchronization methods | |
| US20240070139A1 (en) | Database systems and methods for client-side initiation of server-side actions |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |