CN111381921A - Front-end and back-end separation system and method based on Ambari - Google Patents
Front-end and back-end separation system and method based on Ambari Download PDFInfo
- Publication number
- CN111381921A CN111381921A CN202010142583.7A CN202010142583A CN111381921A CN 111381921 A CN111381921 A CN 111381921A CN 202010142583 A CN202010142583 A CN 202010142583A CN 111381921 A CN111381921 A CN 111381921A
- Authority
- CN
- China
- Prior art keywords
- module
- data resource
- user
- api
- resource request
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/161—Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Data Mining & Analysis (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to a front-end and back-end separation system and a method based on Ambari, which are characterized by comprising the following steps: the system comprises a Web user interface interaction module, more than one server, a monitoring management service module, more than one monitoring end and more than one processing module; the Web user interface interaction module is independently deployed from each server side and is used for providing an interaction interface for a user, sending a request sent by the user to the current server side and carrying out front-end display on information returned by the current server side; and each server side interacts with the Web user interface interaction module, the monitoring management service module and each processing module in a Http reset api mode, and the monitoring management service module interacts with each monitoring side in the Http reset api mode. The invention can be widely applied to the field of data processing.
Description
Technical Field
The invention relates to a front-end and back-end separation system and method based on Ambari, and belongs to the technical field of big data.
Background
Apache Ambari is a Web-based Hadoop distributed cluster configuration management tool, and Ambari makes full use of some existing excellent open source software and skillfully combines the excellent open source software, so that the Ambari has cluster service management capability, monitoring capability and display capability in a distributed environment.
The Ambari framework is mainly composed of two parts: ambari-agent and Ambari-server. Wherein, Ambari-agent: the management monitoring program running on the monitoring node is mainly deployed and depends on python, ruby, puppet, fecter and other tools, and also depends on some monitoring tools such as nagios and ganglia to monitor the cluster condition. The puppet is a distributed cluster configuration management tool, and is also a typical Server/Client mode, the management tool can manage installation configuration deployment of the distributed cluster in a centralized manner, and the main language is ruby. The user interface is a node resource collection library and is used for collecting system information of nodes, such as OS information, the user interface is written in Python language, and the Ambari-agent is also mainly written in Python language, so that the user interface can well collect the node information. Ambari-server: the method is a Server program of Ambari, mainly manages a management monitoring program deployed on each node, and mainly depends on a python tool.
As shown in fig. 1, the Apache Ambari architecture is a distributed architecture Server/agent mode, the backend Server (Ambari Server) bears the functions of component installation, deployment, configuration, monitoring and management, and multiple distributed architectures are stacked together, so that the Ambari architecture is extremely complex, and the secondary development and debugging are extremely inconvenient and flexible.
Disclosure of Invention
In view of the above problems, an object of the present invention is to provide a front-end and back-end separation system and method based on Ambari, in which a front-end Web presentation layer is separated and interacted with a server side through an Api distributor, and all dynamic data of the front-end Web presentation layer are obtained in an Http reset Api manner, and asynchronously invoked, and corresponding real-time resources are obtained from a back-end server, so that the invocation of the front-end Api is not affected by the upgrade of the back-end server.
In order to achieve the purpose, the invention adopts the following technical scheme:
in a first aspect of the invention, there is provided an Ambari-based front-end separation system comprising: the system comprises a Web user interface interaction module, more than one server, a monitoring management service module, more than one monitoring end and more than one processing module; the Web user interface interaction module is independently deployed from each server side and is used for providing an interaction interface for a user, sending a request sent by the user to the current server side and carrying out front-end display on information returned by the current server side; and each server side interacts with the Web user interface interaction module, the monitoring management service module and each processing module in an Http Rest api mode, and the monitoring management service module interacts with each monitoring side in an Http Rest api mode.
Further, the Web user interface interaction module comprises a filter-route, a static resource showing layer, an Api distributor and a static resource server; the filter-router is used for receiving a data resource request sent by a user, dividing the data resource request into a dynamic data resource request and a static data resource request according to the type of the requested data resource, and respectively sending the dynamic data resource request and the static data resource request to the Api distributor and the static resource showing layer; the Api distributor distributes the received dynamic data resource request to the current server side for access, and the accessed dynamic data resource is returned to the corresponding user through the filter-route; and the static resource display layer accesses the static resource server according to the received static data resource request, and the accessed static data resource is returned to the corresponding user through the filter-route.
Further, the static resource presentation layer is used as a view presentation layer of each component and a platform operation basic page resource, and comprises an administrator view module, a yann queue management view module, a file view module, a Hive view module, an Oozine view module and an Tez view module; the administrator view module is used for managing users, including addition or deletion of the users, password modification or permission modification; the Yarn queue management view module is used for graphically managing Yarn; the file view module is used for managing a graphical operation interface of the distributed file storage system; the Hive view module is used for the SQL query function of the hadoop distributed multi-bin Hive graphical interface; the Oozie view module is used for the interface operation function of the hadoop distributed task scheduling engine Oozie; the Tez view module is used to develop the graphical interface operation functionality of the distributed computing engine Tez.
Furthermore, an Api calling module, an information storage module and a server side monitoring module are arranged in the Api distributor; the Api calling module is used for distributing the received dynamic resource request to the current server side and receiving data returned by the server side; the server side monitoring module is used for monitoring the state of each server side and setting the server side in a normal state as the current server side according to a monitoring result and a preset server side priority order list; the information storage module is used for storing cookie information of the user, and the user can conveniently access the current server at any time in the effective range of the cookie information.
Further, the Api calling module distributes the received dynamic data resource request to the current front-end and back-end servers for access, and a doeget method, a doPost method, a doPut method, a doDelete method and a doOptions method are adopted.
Further, before sending a data resource request to the Web user interface interaction module, a user firstly sends a user authentication message, and the Web user interface interaction module sends the authentication message sent by the user to the current server through the Api distributor; and the current server side authenticates the corresponding user according to the received authentication message, generates cookie information of the corresponding user after the authentication is passed, and sends the cookie information to the Api distributor, and the Api distributor stores the cookie information of the user.
In a second aspect of the invention, there is provided a process for an Ambari based front-end separation system comprising the steps of: 1) the user sends an authentication message through the Web user interface interaction module, and the current front-end server and the current back-end server authenticate the corresponding users; 2) after the authentication is passed, the user sends data resource request information through the Web user interface interaction module, and the Web user interface interaction module directly displays the data resources or displays the data resources according to the data resources returned by the current server after accessing the current server.
Further, in step 1), the method for authenticating the corresponding user by the current backend server includes the following steps: 1.1) the user sends an authentication message through a Web user interface interaction module; 1.2) the Web user interface interaction module sends the authentication information of the user to the current server end through an Api distributor; 1.3) the current server side authenticates the corresponding user according to the received authentication message, generates cookie information of the corresponding user after the authentication is passed and sends the cookie information to an Api distributor; 1.4) the Api distributor stores the cookie information of the user and accesses the current server side according to the data resource request sent by the user in the effective range of the cookie information.
Further, in step 2), after the authentication is passed, the user sends the data resource request information through the Web user interface interaction module, and the Web user interface interaction module directly displays the data resource or accesses the current server, and then displays the data resource according to the data resource returned by the current server, including the following steps: 2.1) the filter-routing in the Web user interface interaction module divides the data resource request into a dynamic data resource request and a static data resource request according to the type of the request, sends the dynamic data resource request to an Api distributor and sends the static data resource request to a static resource showing layer; 2.2) the static resource showing layer accesses the static resource server according to the received static data resource request, and the accessed static data resource is returned to the corresponding user through a filter-route; 2.3) the Api distributor distributes the received dynamic data resource request to the current server for access, and the accessed dynamic data resource is returned to the corresponding user through a filter-route.
Due to the adoption of the technical scheme, the invention has the following advantages: 1. according to the invention, the Web user interface interaction module is independent from the server side, the Web user interface interaction module interacts with the server side through the Api distributor, all dynamic data of the front-end Web user interface interaction module are obtained in a restful mode and are asynchronously called, and real-time corresponding resources are obtained from the server side, so that the calling of the front-end Web user interface interaction module cannot be influenced by the upgrading of the server side. 2. In the invention, because a plurality of server ends are arranged, and the server end monitoring modules are arranged in the Api distributor, when the current server end is detected to be abnormal, the server end can be quickly switched to other server ends, thereby ensuring the normal operation of the front-end Web user interface interaction module and increasing the reliability of the system. 3. In the invention, the Api distributor is also internally provided with a server side priority sequence list which can set the priority of the server side for service, thereby further improving the flexibility and reliability of the server side for providing service. Therefore, the method can be widely applied to the technical field of big data.
Drawings
FIG. 1 is a schematic diagram of the conventional open source version of Apache ambari;
FIG. 2 is a schematic diagram of the front-end and back-end separation system architecture of the invention based on Ambari;
FIG. 3 is a schematic diagram of the structure of the WEB side of the front-end and back-end separation system based on Ambari of the invention.
Detailed Description
The invention is described in detail below with reference to the figures and examples.
Firstly, the concept of front-end and back-end separation of the system is introduced, wherein the front-end and back-end separation of the system refers to the following steps: the front-end project and the back-end project are two projects which are placed in two different servers and need to be deployed independently, and the two projects are two different projects, two different code libraries and different developers. The front end only needs to pay attention to the analysis and rendering of the style and the dynamic data of the page, and the back end is focused on specific business logic.
As shown in fig. 2, the present invention provides a front-end and back-end separation system based on Ambari, which includes a Web user interface interaction module, more than one server, a monitoring management service module (Ambari metricc collector), more than one monitoring terminal (Ambari Metric Monitor), and more than one processing module (AmbariAgent). The Web user interface interaction module is independently deployed from each server, and is used for providing an interaction interface for a user, sending a request sent by the user to the current server and carrying out front-end display on information returned by the current server; and each server side interacts with the Web user interface interaction module, the monitoring management service module and each processing module in an Http response mode, and the monitoring management service module interacts with each monitoring side in an Http response api mode.
As shown in FIG. 3, the Web user interface interaction module includes a filter-route, a static resource exposure layer, an Api distributor, and a static resource server; the filter-router is used for receiving a data resource request sent by a user, dividing the data resource request into a dynamic data resource request and a static data resource request according to the type of the requested data resource, and respectively sending the dynamic data resource request and the static data resource request to the Api distributor and the static resource showing layer; the Api distributor distributes the received dynamic data resource request to the current server side for access, and the accessed dynamic data resource is returned to the corresponding user through a filter-route; and the static resource display layer accesses the static resource server according to the received static data resource request, and the accessed static data resource is returned to the corresponding user through a filter-route.
Further, the static resource presentation layer is used as a view presentation layer of each component and a platform operation basic page resource, and comprises an administrator view module, a yann queue management view module, a file view module, a Hive view module, an Oozine view module and an Tez view module. The administrator view module is used for managing users, and comprises user addition or deletion, user password modification or authority modification and the like; the Yarn (Yarn is a computing resource manager of hadoop ecosphere) queue management view module is used for graphically managing Yarn; the file view module is used for a graphical operation interface of the distributed file storage system; the Hive view module is used for the SQL query function of the hadoop distributed multi-bin Hive graphical interface; the Oozie view module is used for the interface operation function of the hadoop distributed task scheduling engine Oozie; tez the view module is used to develop the operation function of the graphical interface of the distributed computing engine tez, Tez is an open source distributed computing engine, which functions as the MapReduce engine but has higher performance than the MapReduce engine.
Further, the static resource server is a java-based jetty server. Of course, other types of Web servers can be used as the static resource presentation layer, and the invention is not limited herein.
Furthermore, an Api calling module, an information storage module and a server side monitoring module are arranged in the Api distributor, wherein the Api calling module is used for distributing the received dynamic resource request to the current server side and receiving data returned by the current server side; the server side monitoring module is used for monitoring the state of each server side and setting the server side in a normal state as a current server side according to a monitoring result and a preset server side priority order list; the information storage module is used for storing cookie information of the user, and the user can conveniently access the current server at any time in the effective range of the cookie information.
Further, when the Api call module distributes the received dynamic data resource request to the current server for access, five methods, i.e., a doeget method, a doPost method, a doPut method, a doDelete method, and a doOptions method, are adopted, and the call methods are well known to those skilled in the art, and are not described herein again.
Further, before a user sends a data resource request to the Web user interface interaction module, a user authentication message needs to be sent first, and the Web user interface interaction module sends the authentication message sent by the user to the current server side through the Api distributor; and the current server side authenticates the corresponding user according to the received authentication message, generates cookie information of the corresponding user after the authentication is passed, and sends the cookie information to the Api distributor, and the Api distributor stores the cookie information of the user so as to access the current server side according to the dynamic data resource request sent by the user in the effective range of the cookie information.
The invention also provides a front-end and back-end separation method based on Ambari, which comprises the following steps:
1) the user sends the authentication information through the Web user interface interaction module, and the current front-end server and the current back-end server authenticate the corresponding user.
2) After the authentication is passed, the user sends data resource request information through the Web user interface interaction module, and the Web user interface interaction module directly displays the data resources or displays the data resources according to the data resources returned by the current server after accessing the current server.
In step 1), the method for authenticating the user by the current back-end server includes the following steps:
1.1) the user sends an authentication message through a Web user interface interaction module;
1.2) the Web user interface interaction module sends the authentication information of the user to the current server end through an Api distributor;
1.3) the current server side authenticates the corresponding user according to the received authentication message, generates cookie information of the corresponding user after the authentication is passed and sends the cookie information to an Api distributor;
1.4) the Api distributor stores the cookie information of the user and accesses the current server side according to the data resource request sent by the user in the effective range of the cookie information.
In the step 2), the method for displaying the data resource by the Web user interface interaction module includes the following steps:
2.1) the filter-routing in the Web user interface interaction module divides the data resource request into a dynamic data resource request and a static data resource request according to the type of the request, sends the dynamic data resource request to an Api distributor and sends the static data resource request to a static resource showing layer;
2.2) the static resource showing layer accesses the static resource server according to the received static data resource request, and the accessed static data resource is returned to the corresponding user through a filter-route;
2.3) the Api distributor distributes the received dynamic data resource request to the current server for access, and the accessed dynamic data resource is returned to the corresponding user through a filter-route.
A specific embodiment is given above, but the invention is not limited to the described embodiment. The basic idea of the present invention lies in the above solution, and it is obvious to those skilled in the art that it is not necessary to spend creative efforts to design various modified models, formulas and parameters according to the teaching of the present invention. Variations, modifications, substitutions and alterations may be made to the embodiments without departing from the principles and spirit of the invention, and still fall within the scope of the invention.
Claims (9)
1. An Ambari-based front-end and back-end separation system, characterized in that it comprises: the system comprises a Web user interface interaction module, more than one server, a monitoring management service module, more than one monitoring end and more than one processing module;
the Web user interface interaction module is independently deployed from each server side and is used for providing an interaction interface for a user, sending a request sent by the user to the current server side and carrying out front-end display on information returned by the current server side;
and each server side interacts with the Web user interface interaction module, the monitoring management service module and each processing module in an Http Rest api mode, and the monitoring management service module interacts with each monitoring side in an Http Rest api mode.
2. An Ambari-based front-end separation system according to claim 1, wherein: the Web user interface interaction module comprises a filter-route, a static resource showing layer, an Api distributor and a static resource server;
the filter-router is used for receiving a data resource request sent by a user, dividing the data resource request into a dynamic data resource request and a static data resource request according to the type of the requested data resource, and respectively sending the dynamic data resource request and the static data resource request to the Api distributor and the static resource showing layer;
the Api distributor distributes the received dynamic data resource request to the current server side for access, and the accessed dynamic data resource is returned to the corresponding user through the filter-route;
and the static resource display layer accesses the static resource server according to the received static data resource request, and the accessed static data resource is returned to the corresponding user through the filter-route.
3. An Ambari-based front-end separation system according to claim 2, wherein: the static resource showing layer is used as a view showing layer of each component and a platform operation basic page resource and comprises an administrator view module, a Yarn queue management view module, a file view module, a Hive view module, an Oozine view module and an Tez view module;
the administrator view module is used for managing users, including addition or deletion of the users, password modification or permission modification;
the Yarn queue management view module is used for graphically managing Yarn;
the file view module is used for managing a graphical operation interface of the distributed file storage system;
the Hive view module is used for the SQL query function of the hadoop distributed multi-bin Hive graphical interface;
the Oozie view module is used for the interface operation function of the hadoop distributed task scheduling engine Oozie;
the Tez view module is used to develop the graphical interface operation functionality of the distributed computing engine Tez.
4. An Ambari-based front-end separation system according to claim 2, wherein: an Api calling module, an information storage module and a server side monitoring module are arranged in the Api distributor;
the Api calling module is used for distributing the received dynamic resource request to the current server side and receiving data returned by the server side;
the server side monitoring module is used for monitoring the state of each server side and setting the server side in a normal state as the current server side according to a monitoring result and a preset server side priority order list;
the information storage module is used for storing cookie information of the user, and the user can conveniently access the current server at any time in the effective range of the cookie information.
5. An Ambari-based front-end separation system according to claim 4, wherein: and when the Api calling module distributes the received dynamic data resource request to the current front-end server and the current back-end server for access, a DoGet method, a Dopost method, a DoPut method, a DoDelete method and a DoOptions method are adopted.
6. An Ambari-based front-end separation system according to claim 2, wherein: before a user sends a data resource request to the Web user interface interaction module, firstly, a user authentication message is sent, and the Web user interface interaction module sends the authentication message sent by the user to the current server side through the Api distributor; and the current server side authenticates the corresponding user according to the received authentication message, generates cookie information of the corresponding user after the authentication is passed, and sends the cookie information to the Api distributor, and the Api distributor stores the cookie information of the user.
7. A process employing an Ambari-based front-end separation system according to any of claims 1 to 6, characterized by the steps of:
1) the user sends an authentication message through the Web user interface interaction module, and the current front-end server and the current back-end server authenticate the corresponding users;
2) after the authentication is passed, the user sends data resource request information through the Web user interface interaction module, and the Web user interface interaction module directly displays the data resources or displays the data resources according to the data resources returned by the current server after accessing the current server.
8. A process according to claim 7 for front-end and back-end separation based on Ambari, characterized in that: in step 1), the method for authenticating the corresponding user by the current back-end server includes the following steps:
1.1) the user sends an authentication message through a Web user interface interaction module;
1.2) the Web user interface interaction module sends the authentication information of the user to the current server end through an Api distributor;
1.3) the current server side authenticates the corresponding user according to the received authentication message, generates cookie information of the corresponding user after the authentication is passed and sends the cookie information to an Api distributor;
1.4) the Api distributor stores the cookie information of the user and accesses the current server side according to the data resource request sent by the user in the effective range of the cookie information.
9. A process according to claim 7 for front-end and back-end separation based on Ambari, characterized in that: in the step 2), after the authentication is passed, the user sends the data resource request information through the Web user interface interaction module, and the Web user interface interaction module directly displays the data resource or accesses the current server, and then displays the data resource according to the data resource returned by the current server, which includes the following steps:
2.1) the filter-routing in the Web user interface interaction module divides the data resource request into a dynamic data resource request and a static data resource request according to the type of the request, sends the dynamic data resource request to an Api distributor and sends the static data resource request to a static resource showing layer;
2.2) the static resource showing layer accesses the static resource server according to the received static data resource request, and the accessed static data resource is returned to the corresponding user through a filter-route;
2.3) the Api distributor distributes the received dynamic data resource request to the current server for access, and the accessed dynamic data resource is returned to the corresponding user through a filter-route.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010142583.7A CN111381921B (en) | 2020-03-04 | 2020-03-04 | Front-end and back-end separation system and method based on Ambari |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010142583.7A CN111381921B (en) | 2020-03-04 | 2020-03-04 | Front-end and back-end separation system and method based on Ambari |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111381921A true CN111381921A (en) | 2020-07-07 |
| CN111381921B CN111381921B (en) | 2020-10-09 |
Family
ID=71217147
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010142583.7A Active CN111381921B (en) | 2020-03-04 | 2020-03-04 | Front-end and back-end separation system and method based on Ambari |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111381921B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113220273A (en) * | 2021-05-20 | 2021-08-06 | 南方电网数字电网研究院有限公司 | Micro front-end application resource processing method, device, equipment and medium |
| CN113220273B (en) * | 2021-05-20 | 2024-06-04 | 南方电网数字电网研究院有限公司 | Micro front-end application resource processing method, device, equipment and medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8055800B1 (en) * | 2007-06-29 | 2011-11-08 | Extreme Networks, Inc. | Enforcing host routing settings on a network device |
| CN105138448A (en) * | 2014-06-05 | 2015-12-09 | 北京畅游天下网络技术有限公司 | Method and device for page test at front end |
| CN106844467A (en) * | 2016-12-21 | 2017-06-13 | 大唐网络有限公司 | Method for exhibiting data and device |
| CN107133020A (en) * | 2016-02-26 | 2017-09-05 | 中移(苏州)软件技术有限公司 | A kind of data processing method, system, interface end and server |
| CN107273528A (en) * | 2017-06-28 | 2017-10-20 | 努比亚技术有限公司 | A kind of front and back end separation method, mobile terminal and computer-readable recording medium |
| CN107562427A (en) * | 2017-09-07 | 2018-01-09 | 南威软件股份有限公司 | A kind of Page Template engine renders method based on NodeJS |
| CN107590145A (en) * | 2016-07-06 | 2018-01-16 | 北京神州泰岳软件股份有限公司 | A kind for the treatment of method and apparatus of page static resource |
| CN108319506A (en) * | 2017-01-17 | 2018-07-24 | 贵州白山云科技有限公司 | A kind of data hierarchy processing method and processing device |
| CN109697130A (en) * | 2017-10-23 | 2019-04-30 | 北京金山云网络技术有限公司 | Front and back end separation method, device, equipment and the storage medium of web system |
| US20190154439A1 (en) * | 2016-03-04 | 2019-05-23 | May Patents Ltd. | A Method and Apparatus for Cooperative Usage of Multiple Distance Meters |
| CN110134564A (en) * | 2019-03-29 | 2019-08-16 | 山东浪潮云信息技术有限公司 | A kind of visual Kafka cluster monitoring method |
-
2020
- 2020-03-04 CN CN202010142583.7A patent/CN111381921B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8055800B1 (en) * | 2007-06-29 | 2011-11-08 | Extreme Networks, Inc. | Enforcing host routing settings on a network device |
| CN105138448A (en) * | 2014-06-05 | 2015-12-09 | 北京畅游天下网络技术有限公司 | Method and device for page test at front end |
| CN107133020A (en) * | 2016-02-26 | 2017-09-05 | 中移(苏州)软件技术有限公司 | A kind of data processing method, system, interface end and server |
| US20190154439A1 (en) * | 2016-03-04 | 2019-05-23 | May Patents Ltd. | A Method and Apparatus for Cooperative Usage of Multiple Distance Meters |
| CN107590145A (en) * | 2016-07-06 | 2018-01-16 | 北京神州泰岳软件股份有限公司 | A kind for the treatment of method and apparatus of page static resource |
| CN106844467A (en) * | 2016-12-21 | 2017-06-13 | 大唐网络有限公司 | Method for exhibiting data and device |
| CN108319506A (en) * | 2017-01-17 | 2018-07-24 | 贵州白山云科技有限公司 | A kind of data hierarchy processing method and processing device |
| CN107273528A (en) * | 2017-06-28 | 2017-10-20 | 努比亚技术有限公司 | A kind of front and back end separation method, mobile terminal and computer-readable recording medium |
| CN107562427A (en) * | 2017-09-07 | 2018-01-09 | 南威软件股份有限公司 | A kind of Page Template engine renders method based on NodeJS |
| CN109697130A (en) * | 2017-10-23 | 2019-04-30 | 北京金山云网络技术有限公司 | Front and back end separation method, device, equipment and the storage medium of web system |
| CN110134564A (en) * | 2019-03-29 | 2019-08-16 | 山东浪潮云信息技术有限公司 | A kind of visual Kafka cluster monitoring method |
Non-Patent Citations (1)
| Title |
|---|
| 孟祥双: ""前后端分离式WEB应用开发研究"", 《电子元器件与信息技术》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113220273A (en) * | 2021-05-20 | 2021-08-06 | 南方电网数字电网研究院有限公司 | Micro front-end application resource processing method, device, equipment and medium |
| CN113220273B (en) * | 2021-05-20 | 2024-06-04 | 南方电网数字电网研究院有限公司 | Micro front-end application resource processing method, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111381921B (en) | 2020-10-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200177373A1 (en) | System and method for storing contract data structures on permissioned distributed ledgers | |
| US9413604B2 (en) | Instance host configuration | |
| US9558042B2 (en) | System and method providing object messages in a compute environment | |
| US9794135B2 (en) | Managed service for acquisition, storage and consumption of large-scale data streams | |
| US9276959B2 (en) | Client-configurable security options for data streams | |
| US9712410B1 (en) | Local metrics in a service provider environment | |
| US11294758B2 (en) | Automated methods and systems to classify and troubleshoot problems in information technology systems and services | |
| CA2898478C (en) | Instance host configuration | |
| EP1654648B1 (en) | Hierarchical management of the dynamic allocation of resources in a multi-node system | |
| Trihinas et al. | Monitoring elastically adaptive multi-cloud services | |
| US8966025B2 (en) | Instance configuration on remote platforms | |
| CN109766241A (en) | System monitoring method, apparatus, computer equipment and computer readable storage medium | |
| US11689536B1 (en) | Server-based restricted access storage | |
| Bunch et al. | Appscale: open-source platform-as-a-service | |
| Zareian et al. | A big data framework for cloud monitoring | |
| CN112685499A (en) | Method, device and equipment for synchronizing process data of work service flow | |
| CN109902028A (en) | Automated testing method, device, equipment and the storage medium of ACL characteristic | |
| CN114338684B (en) | Energy management system and method | |
| US10122602B1 (en) | Distributed system infrastructure testing | |
| Albrecht et al. | Making work queue cluster-friendly for data intensive scientific applications | |
| US10893015B2 (en) | Priority topic messaging | |
| CN116775420A (en) | Information creation cloud platform resource display and early warning method and system based on Flink flow calculation | |
| CN111381921B (en) | Front-end and back-end separation system and method based on Ambari | |
| US10706073B1 (en) | Partitioned batch processing for a usage analysis system | |
| US10348596B1 (en) | Data integrity monitoring for a usage analysis system |
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 | ||
| CP03 | Change of name, title or address |
Address after: 301, 3 / F, block F, Zhizao street, Zhongguancun, 45 Chengfu Road, Haidian District, Beijing 100062 Patentee after: Beijing Dongfang Jinxin Technology Co.,Ltd. Address before: 9 / F, Jiahe Guoxin building, 15 Baiqiao street, Dongcheng District, Beijing 100062 Patentee before: Beijing Dongfang Jinxin Technology Co.,Ltd. |
|
| CP03 | Change of name, title or address |