CN113220486A - Distributed system with separated front and back ends and service calling method, medium and product thereof - Google Patents

Distributed system with separated front and back ends and service calling method, medium and product thereof Download PDF

Info

Publication number
CN113220486A
CN113220486A CN202110587850.6A CN202110587850A CN113220486A CN 113220486 A CN113220486 A CN 113220486A CN 202110587850 A CN202110587850 A CN 202110587850A CN 113220486 A CN113220486 A CN 113220486A
Authority
CN
China
Prior art keywords
service
calling
module
distributed
user
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
Application number
CN202110587850.6A
Other languages
Chinese (zh)
Inventor
刘利勇
曹黎明
赵爱新
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202110587850.6A priority Critical patent/CN113220486A/en
Publication of CN113220486A publication Critical patent/CN113220486A/en
Pending legal-status Critical Current

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/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G06F9/548—Object oriented; Remote method invocation [RMI]
    • 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/46—Multiprogramming arrangements
    • G06F9/465—Distributed object oriented systems

Abstract

The disclosure provides a distributed system with separated front and back ends and a service calling method thereof, which can be applied to the technical field of distributed computing. The distributed system with the separated front end and the separated rear end comprises a system front end and a system rear end, wherein: the system front end is used for realizing interaction with a user, calling the service provided by the system back end in a remote process calling mode and obtaining a service calling result returned by the system back end; and the system back end is used for receiving the calling of the system front end to the service and providing the service calling result. Based on the distributed service framework, the system function is divided into the distributed services, and the front-end display and the back-end service are separated, so that the problem that maintenance is not facilitated due to the coupling of front-end and back-end codes is solved, the compiling time is reduced, and the deployment convenience and the system expansibility are improved.

Description

Distributed system with separated front and back ends and service calling method, medium and product thereof
Technical Field
The present disclosure relates to the field of distributed computing technologies, and in particular, to a distributed system with separated front and back ends, and a service invocation method, medium, and product thereof.
Background
At present, the architecture of many financial institutions is a typical single-body structure system, the single-body structure system generally consists of a reverse proxy server, a database and an application, all service modules are packaged in one application to run, and for high-availability consideration, the application deploys at least two nodes.
The monolithic architecture system has many of its own advantages when the service is simple: the development and test are simple, the deployment is simple, the capacity expansion is simple, and only machines are added to the application. However, the single-structure system has many disadvantages, especially after the service scale becomes complicated, the disadvantages are very prominent, which mainly appear as follows: the development efficiency is seriously influenced by various problems of slow compiling, slow starting, code conflict and the like, the performance expansion has limitation, and the performance is difficult to expand by a simple stacking machine mode after a certain scale is reached. Therefore, the current single structure system cannot meet the fast online and high availability requirements of the current business requirements under the background of the rapid development of the business.
The distributed service framework mainly provides a light-weight framework for encapsulation of service definition, registration, subscription and invocation, can perfectly solve the problems of the single structure system, can meet the requirements of high concurrency and high availability of a financial system along with rapid development and perfection of the distributed service framework, and has mature transformation opportunity.
Disclosure of Invention
In view of the defects in the prior art, the present disclosure provides a distributed system with separated front and back ends, and a service calling method, medium, and product thereof, which solve the problem of being not favorable for maintenance due to front and back end code coupling by splitting system functions into front end display and back end service based on a distributed service framework, reduce compiling time, and improve deployment convenience and system extensibility.
According to a first aspect of the present disclosure, there is provided a front-end separated distributed system comprising a system front-end and a system back-end, wherein:
the system front end is used for realizing information interaction with a user, calling the service provided by the system back end in a remote process calling mode and obtaining a service calling result returned by the system back end;
and the system back end is used for receiving the calling of the system front end to the service, executing the service called by the system front end and returning the service calling result to the system front end.
According to the embodiment of the present disclosure, the system front end includes a front end service group, a WEB service group, a message assembly module, and a message transceiver module, wherein:
the front-end service group is used for deploying a dynamic page of a business function and realizing information interaction with a user;
the WEB service group is used for deploying a static page of a business function and carrying out static verification on user interaction information;
the message assembling module is used for assembling the user interaction information into a service request message;
the message receiving and sending module is used for acquiring a service list, determining a service provider, calling the service provided by the service provider at the back end of the system in a remote procedure calling mode, and receiving a service calling result returned by the service provider at the back end of the system.
According to the embodiment of the disclosure, the dynamic page of the business function comprises at least one of an information submission dynamic page, an authorization dynamic page and a query dynamic page, and the user interaction information is information of interaction between a user and the dynamic page of the business function.
According to an embodiment of the present disclosure, the system backend includes a database, a common service module, a service providing module, and a service returning module, wherein:
the database is used for carrying out fragment storage on data;
the public service module is used for realizing a service routing function;
the service providing module is used for splitting different service modules and/or entities into different services and providing the different services for the system front end;
and the service returning module is used for returning a service calling result to the front end of the system after the called service is executed.
According to an embodiment of the present disclosure, the returning of the service invocation result to the system front end specifically includes:
and returning a service calling result to the system front end by sending a JSON message.
According to an embodiment of the present disclosure, the system further comprises a registry, wherein:
the registry is used for receiving a service subscription request of the system front end, receiving a service registered by the system back end, and notifying the registered service to the system front end.
According to an embodiment of the present disclosure, the system front-end further includes a service subscription module, wherein:
the service subscription module is used for sending the service subscription request to the registry to subscribe to the service, and receiving the service notification message sent by the registry to update the locally stored service list.
According to an embodiment of the present disclosure, the system backend further includes a service registration module, wherein:
the service registration module is used for registering service with the registration center.
According to an embodiment of the present disclosure, the registering a service with the registry specifically includes: and reading a locally stored configuration file to acquire a service to be registered, and sending a service registration request to the registration center to complete service registration.
A second aspect of the present disclosure provides a service invocation method for a distributed system based on front-end and back-end separation, where the distributed system includes a system front end and a system back end, and the service invocation method includes the following steps:
the system front end carries out information interaction with a user and calls a service provided by the system back end in a remote process calling mode;
the system back end receives the calling of the system front end to the service, executes the service called by the system front end, and returns a service calling result to the system front end;
and the front end of the system receives a service calling result returned by the back end of the system.
According to the embodiment of the disclosure, the system front end performs information interaction with a user, and calls a service provided by the system back end in a remote procedure call mode, specifically:
the information interaction with the user is realized by deploying the dynamic page of the service function through a front-end service group in the front end of the system;
static verification is carried out on user interaction information through a static page of a WEB service group deployment service function in the front end of the system;
assembling the user interaction information into a service request message;
and acquiring a service list, determining a service provider, and calling the service provided by the service provider at the back end of the system in a remote procedure calling mode.
According to the embodiment of the disclosure, the dynamic page of the business function comprises at least one of an information submission dynamic page, an authorization dynamic page and a query dynamic page, and the user interaction information is information of interaction between a user and the dynamic page of the business function.
According to the embodiment of the present disclosure, the system back end receives the call of the system front end to the service, executes the service called by the system front end, and returns a service calling result to the system front end, specifically:
the system back end receives the call of the system front end to the service;
realizing service routing through a public service module in the system back end;
executing the service called by the system front end through a service providing module in the system rear end;
and returning a service calling result to the system front end.
According to an embodiment of the present disclosure, the returning of the service invocation result to the system front end specifically includes:
and returning a service calling result to the system front end by sending a JSON message.
According to the embodiment of the disclosure, before the system front end interacts with a user and calls the service provided by the system back end in a remote procedure call mode, the method further comprises:
the system backend registers services with a registry.
According to the embodiment of the disclosure, the registration service of the system back end to the registry specifically comprises:
and the back end of the system reads the locally stored configuration file to acquire the service to be registered, and sends a service registration request to the registration center to complete service registration.
According to the embodiment of the disclosure, before the system front end interacts with a user and calls the service provided by the system back end in a remote procedure call mode, the method further comprises:
the system front end sends a service subscription request to a registry to subscribe to a service, and receives a service notification message sent by the registry to update a locally stored service list.
A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the service invocation method described above.
A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described service invocation method.
A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above-described service invocation method.
Compared with the prior art, the distributed system with the front-end and the back-end separated and the service calling method, medium and product thereof have the advantages that based on a distributed service framework, system functions are split into distributed services, front-end display and back-end services are separated, developers are enabled to concentrate on modules in charge of the developers, the problem that due to front-end code coupling, maintenance is not facilitated is solved, function expansibility and reusability are improved, different services can be assembled to form new service functions according to service dimension multiplexing, a light-weight deployment version library is formed by splitting a front-end group and a back-end group, compiling time is reduced, and deployment convenience and system expansibility are improved.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:
FIG. 1 schematically illustrates a block diagram of components of a front-end separated distributed system according to an embodiment of the disclosure;
FIG. 2 is a flow chart schematically illustrating a method for service invocation in a distributed system based on front-end separation according to an embodiment of the present disclosure;
fig. 3 schematically illustrates a block diagram of an electronic device adapted to implement a service invocation method for a distributed system based on front-end separation according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
The embodiment of the disclosure provides a distributed system with separated front and back ends, which comprises a system front end and a system back end, wherein the system front end is used for realizing interaction with a user, calling a service provided by the system back end in a remote process calling mode, and obtaining a service calling result returned by the system back end; the system front end comprises a front end service group, a WEB service group, a message assembling module and a message receiving and transmitting module, wherein: the front-end service group is used for deploying a dynamic page of a business function and realizing information interaction with a user; the WEB service group is used for deploying a static page of a business function and carrying out static verification on user interaction information; the message assembling module is used for assembling the user interaction information into a service request message; the message receiving and sending module is used for acquiring a service list, determining a service provider, calling the service provided by the service provider at the back end of the system in a remote procedure calling mode, and receiving a service calling result returned by the service provider at the back end of the system. And the system back end is used for receiving the calling of the system front end to the service, executing the service called by the system front end and returning the service calling result to the system front end. The system back end comprises a database, a public service module, a service providing module and a service returning module, wherein: the database is used for carrying out fragment storage on data; the public service module is used for realizing a service routing function; the service providing module is used for splitting different service modules and/or entities into different services and providing the different services for the system front end; and the service returning module is used for returning a service calling result to the front end of the system after the called service is executed.
By means of the system of the embodiment, the system functions are split into distributed services, and the front-end display and the back-end service are separated, so that developers can concentrate on modules in charge of the developers, the problem that the front-end code and the back-end code are not beneficial to maintenance due to coupling is solved, the function expansibility and the reusability are improved, different services can be assembled according to service dimension multiplexing to form new service functions, a light-weight deployment version library is formed by splitting a front-end group and a back-end group, the compiling time is reduced, and the deployment convenience and the system expansibility are improved.
A front-end and back-end separated distributed system and a service invocation method, medium and product thereof according to embodiments of the present disclosure will be described in detail below with reference to fig. 1-3.
Fig. 1 schematically shows a block diagram of components of a front-end separated distributed system according to an embodiment of the present disclosure, by means of which an embodiment provided by the present disclosure is described.
As shown in fig. 1, this embodiment provides a front-end and back-end separated distributed system, which includes a system front-end 100 and a system back-end 200, wherein:
the system front end 100 is configured to implement information interaction with a user, assemble a service request packet, Call a service provided by the system back end 200 in a Remote Procedure Call (RPC) manner, and obtain a service Call result returned by the system back end 200.
The system front end 100 is further configured to subscribe to a service provided by the system back end 200.
The system front end 100 includes a front end service group 101, a WEB service group 102, a message assembling module 103, and a message transceiving module 104, where:
the front-end service group 101 is configured to deploy a dynamic page of a service function to implement information interaction with a user, where the dynamic page of the service function includes at least one of an information submission dynamic page, an authorization dynamic page, and an inquiry dynamic page.
The WEB service group 102 is configured to deploy a static page with a business function, and perform static verification of user interaction information of an information submission dynamic page, an authorization dynamic page, and an inquiry dynamic page.
The message assembling module 103 is configured to assemble the user interaction information into a service request message.
The message transceiver module 104 is configured to obtain a service list and further obtain a service provider, Call a service provided by the service provider of the system backend 200 in a Remote Procedure Call (RPC) manner, and receive a service Call result returned by the service provider of the system backend 200.
The system front-end 100 further comprises a service subscription module 105, the service subscription module 105 being configured to subscribe to services and update the service list based on the received service notifications.
Further, the system may further include a registry 300, where the registry 300 is configured to receive a service subscription request of the system front end 100, receive a service registered by the system back end 200, and notify the system front end 100 of the service. Further, the service subscription module 105 may send a service subscription request to the registry 300 to subscribe to a service, and receive a service notification message sent by the registry 300 to update a locally stored service list.
The system back end 200 is configured to register a service, receive a call of the system front end 100 to the service, execute the called service, and return the service call result to the system front end 100.
The system backend 200 includes a database 201, a common service module 202, a service providing module 203, and a service returning module 204, wherein:
the database 201 is used for performing fragment storage on data.
The common service module 202 is configured to implement a service routing function.
The service providing module 203 is configured to split different service modules and/or entities into different services, and provide the different services.
The service returning module 204 is configured to return a service calling result to the system front end 100 after the called service is executed. Specifically, a service invocation result may be returned to the system front end 100 by sending a JSON packet.
The system backend 200 further includes a service registration module 205, and the service registration module 205 is configured to perform service registration with the registry 300. Specifically, the service registration module 205 may read a locally stored configuration file to obtain a service to be registered, and send a service registration request to the registry 300 to complete service registration.
Based on a distributed service framework, by splitting system functions into distributed services and separating front-end display and back-end services, developers can concentrate on modules in charge of the developers, the problem that maintenance is not facilitated due to front-end code coupling is solved, function expansibility and reusability are improved, different services can be assembled to form new service functions according to service dimension multiplexing, a lightweight deployment version library is formed by splitting a front-end group and a back-end group, compiling time is reduced, and deployment convenience and system expansibility are improved.
Fig. 2 schematically shows a flowchart of a service invocation method of a distributed system based on front-end separation according to an embodiment of the present disclosure, and the embodiment provided by the present disclosure is described by means of the flowchart of the method.
As shown in fig. 2, the embodiment provides a service invocation method for a distributed system based on front-end and back-end separation, where the distributed system includes a system front end and a system back end, and a specific architecture of the distributed system is as shown in fig. 1, where the service invocation method specifically includes operation S101-operation S105, and specifically as follows:
in operation S101, the system backend 200 registers for service.
The system backend 200 registration service specifically includes: the system backend 200 registers services with the registry 300. More specifically, the system backend 200 reads a locally stored configuration file to obtain a service to be registered, and sends a service registration request to the registration center 300 to complete registration of the service.
In operation S102, the system front end 100 subscribes to a service and updates a service list based on the received service notification.
The system front end 100 subscribes to a service and updates a service list based on the received service notification, specifically: the system front end 100 sends a service subscription request to the registry 300 to subscribe to a service, and receives a service notification message sent by the registry 300 to update a locally stored service list.
In operation S103, the system front end 100 interacts with a user and calls a service provided by the system back end 200 in a Remote Procedure Call (RPC) manner.
The system front end 100 interacts with a user, specifically: the system front end 100 deploys a dynamic page of a business function through a front end service group 101 in the system front end to realize information interaction with a user, deploys a static page of the business function through a WEB service group 102 in the system front end to perform static verification of user interaction information, and then assembles the user interaction information into a service request message. The dynamic page of the business function comprises at least one of an information submission dynamic page, an authorization dynamic page and a query dynamic page, and the user interaction information is information of interaction between a user and the dynamic page of the business function.
The system front end 100 calls the service provided by the system back end 200 in a Remote Procedure Call (RPC) mode, specifically: the system front end 100 obtains the service list and then obtains the service provider, and calls the service provided by the service provider of the system back end 200 in a Remote Procedure Call (RPC) manner.
In operation S104, the system back end 200 receives the call of the system front end 100 to the service, executes the service called by the system front end 100, and returns a corresponding service call result to the system front end 100.
The system back end 200 receives the call of the system front end 100 to the service, executes the service called by the system front end 100, and returns a corresponding service call result to the system front end 100, specifically: the system backend 200 receives the call of the system front end 100 to the service, implements service routing through the common service module 202 in the system backend 200, executes the service called by the system front end 100 through the service providing module 203 in the system backend 200, and returns a corresponding service calling result to the system front end 100, specifically, may return the corresponding service calling result to the system front end 100 by sending a JSON message.
In operation S105, the system front end 100 receives a service invocation result provided by the system back end 200.
According to the service calling method of the distributed system based on the front-end and back-end separation, the system functions are separated into the distributed services, the front-end display and the back-end services are separated, developers are enabled to concentrate on modules in charge of the developers, the problem that maintenance is not facilitated due to front-end and back-end code coupling is solved, the function expansibility and the reusability are improved, different services can be assembled to form new service functions according to service dimension multiplexing, a light-weight deployment version library is formed by separating front-end and back-end groups, compiling time is shortened, and deployment convenience and system expansibility are improved.
FIG. 3 schematically illustrates a block diagram of an electronic device suitable for implementing a service invocation method in a distributed computing in accordance with an embodiment of the present disclosure.
As shown in fig. 3, an electronic device 400 according to an embodiment of the present disclosure includes a processor 401 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)402 or a program loaded from a storage section 408 into a Random Access Memory (RAM) 403. Processor 401 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 401 may also include onboard memory for caching purposes. Processor 401 may include a single processing unit or multiple processing units for performing the different actions of the method flows in accordance with embodiments of the present disclosure.
In the RAM 403, various programs and data necessary for the operation of the electronic apparatus 400 are stored. The processor 401, ROM 402 and RAM 403 are connected to each other by a bus 404. The processor 401 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 402 and/or the RAM 403. Note that the programs may also be stored in one or more memories other than the ROM 402 and RAM 403. The processor 401 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, electronic device 400 may also include an input/output (I/O) interface 405, input/output (I/O) interface 405 also being connected to bus 404. Electronic device 400 may also include one or more of the following components connected to I/O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output section 407 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 408 including a hard disk and the like; and a communication section 409 including a network interface card such as a LAN card, a modem, or the like. The communication section 409 performs communication processing via a network such as the internet. A driver 410 is also connected to the I/O interface 405 as needed. A removable medium 411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 410 as necessary, so that a computer program read out therefrom is mounted into the storage section 408 as necessary.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include ROM 402 and/or RAM 403 and/or one or more memories other than ROM 402 and RAM 403 described above.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the item recommendation method provided by the embodiment of the disclosure.
The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 401. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, downloaded and installed through the communication section 409, and/or installed from the removable medium 411. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 409, and/or installed from the removable medium 411. The computer program, when executed by the processor 401, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (20)

1. A front-end separated distributed system, the distributed system comprising a system front-end and a system back-end, wherein:
the system front end is used for realizing information interaction with a user, calling the service provided by the system back end in a remote process calling mode and obtaining a service calling result returned by the system back end;
and the system back end is used for receiving the calling of the system front end to the service, executing the service called by the system front end and returning the service calling result to the system front end.
2. The front-end separated distributed system according to claim 1, wherein: the system front end comprises a front end service group, a WEB service group, a message assembling module and a message receiving and transmitting module, wherein:
the front-end service group is used for deploying a dynamic page of a business function and realizing information interaction with a user;
the WEB service group is used for deploying a static page of a business function and carrying out static verification on user interaction information;
the message assembling module is used for assembling the user interaction information into a service request message;
the message receiving and sending module is used for acquiring a service list, determining a service provider, calling the service provided by the service provider at the back end of the system in a remote procedure calling mode, and receiving a service calling result returned by the service provider at the back end of the system.
3. The front-end separated distributed system according to claim 2, wherein: the dynamic page of the business function comprises at least one of an information submission dynamic page, an authorization dynamic page and a query dynamic page, and the user interaction information is information of interaction between a user and the dynamic page of the business function.
4. The front-end separated distributed system according to any of claims 1-3, wherein: the system back end comprises a database, a public service module, a service providing module and a service returning module, wherein:
the database is used for carrying out fragment storage on data;
the public service module is used for realizing a service routing function;
the service providing module is used for splitting different service modules and/or entities into different services and providing the different services for the system front end;
and the service returning module is used for returning a service calling result to the front end of the system after the called service is executed.
5. The front-end separated distributed system according to claim 4, wherein: the returning of the service calling result to the system front end specifically includes:
and returning a service calling result to the system front end by sending a JSON message.
6. The front-end separated distributed system according to claim 1, wherein: the system further comprises a registry, wherein:
the registry is used for receiving a service subscription request of the system front end, receiving a service registered by the system back end, and notifying the registered service to the system front end.
7. The front-end separated distributed system according to claim 6, wherein: the system front-end further comprises a service subscription module, wherein:
the service subscription module is used for sending the service subscription request to the registry to subscribe to the service, and receiving the service notification message sent by the registry to update the locally stored service list.
8. The front-end separated distributed system according to claim 6, wherein: the system backend further comprises a service registration module, wherein:
the service registration module is used for registering service with the registration center.
9. The front-end separated distributed system according to claim 8, wherein: the registering service with the registry specifically includes: and reading a locally stored configuration file to acquire a service to be registered, and sending a service registration request to the registration center to complete service registration.
10. A service calling method of a distributed system based on front-end and back-end separation is characterized in that the distributed system comprises a system front end and a system back end, and the service calling method comprises the following steps:
the system front end carries out information interaction with a user and calls a service provided by the system back end in a remote process calling mode;
the system back end receives the calling of the system front end to the service, executes the service called by the system front end, and returns a service calling result to the system front end;
and the front end of the system receives a service calling result returned by the back end of the system.
11. The service invocation method for distributed systems based on front-end separation according to claim 10, wherein: the system front end carries out information interaction with a user, and calls a service provided by the system rear end in a remote process calling mode, wherein the method specifically comprises the following steps:
the information interaction with the user is realized by deploying the dynamic page of the service function through a front-end service group in the front end of the system;
static verification is carried out on user interaction information through a static page of a WEB service group deployment service function in the front end of the system;
assembling the user interaction information into a service request message;
and acquiring a service list, determining a service provider, and calling the service provided by the service provider at the back end of the system in a remote procedure calling mode.
12. The service invocation method for distributed systems based on front-end separation according to claim 11, wherein: the dynamic page of the business function comprises at least one of an information submission dynamic page, an authorization dynamic page and a query dynamic page, and the user interaction information is information of interaction between a user and the dynamic page of the business function.
13. The service invocation method for a distributed system based on front-end separation according to any of claims 10-12, wherein: the system back end receives the call of the system front end to the service, executes the service called by the system front end, and returns a service calling result to the system front end, which specifically comprises the following steps:
the system back end receives the call of the system front end to the service;
realizing service routing through a public service module in the system back end;
executing the service called by the system front end through a service providing module in the system rear end;
and returning a service calling result to the system front end.
14. The service invocation method for distributed systems based on front-end separation according to claim 13, wherein: the returning of the service calling result to the system front end specifically includes:
and returning a service calling result to the system front end by sending a JSON message.
15. The service invocation method for distributed systems based on front-end separation according to claim 10, wherein: before the system front end interacts with a user and calls a service provided by the system back end in a remote procedure call mode, the method further comprises the following steps:
the system backend registers services with a registry.
16. The service invocation method for distributed systems based on front-end separation according to claim 15, wherein: the system back end registers service with a registration center, specifically:
and the back end of the system reads the locally stored configuration file to acquire the service to be registered, and sends a service registration request to the registration center to complete service registration.
17. The service invocation method for distributed system based on front-end separation according to claim 10, 15 or 16, wherein: before the system front end interacts with a user and calls a service provided by the system back end in a remote procedure call mode, the method further comprises the following steps:
the system front end sends a service subscription request to a registry to subscribe to a service, and receives a service notification message sent by the registry to update a locally stored service list.
18. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 10-17.
19. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 10 to 17.
20. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 10 to 17.
CN202110587850.6A 2021-05-27 2021-05-27 Distributed system with separated front and back ends and service calling method, medium and product thereof Pending CN113220486A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110587850.6A CN113220486A (en) 2021-05-27 2021-05-27 Distributed system with separated front and back ends and service calling method, medium and product thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110587850.6A CN113220486A (en) 2021-05-27 2021-05-27 Distributed system with separated front and back ends and service calling method, medium and product thereof

Publications (1)

Publication Number Publication Date
CN113220486A true CN113220486A (en) 2021-08-06

Family

ID=77099670

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110587850.6A Pending CN113220486A (en) 2021-05-27 2021-05-27 Distributed system with separated front and back ends and service calling method, medium and product thereof

Country Status (1)

Country Link
CN (1) CN113220486A (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110296050A1 (en) * 2010-05-28 2011-12-01 Microsoft Corporation Realtime websites with publication and subscription
CN105472003A (en) * 2015-12-11 2016-04-06 珠海金山网络游戏科技有限公司 Large-scale distributed game server system and implementation method thereof
CN107517139A (en) * 2016-06-17 2017-12-26 阿里巴巴集团控股有限公司 Data processing method and system, device test system and bus test system
CN109889381A (en) * 2019-02-18 2019-06-14 国家计算机网络与信息安全管理中心 Automatic configuration management method and device based on fort machine

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110296050A1 (en) * 2010-05-28 2011-12-01 Microsoft Corporation Realtime websites with publication and subscription
CN105472003A (en) * 2015-12-11 2016-04-06 珠海金山网络游戏科技有限公司 Large-scale distributed game server system and implementation method thereof
CN107517139A (en) * 2016-06-17 2017-12-26 阿里巴巴集团控股有限公司 Data processing method and system, device test system and bus test system
CN109889381A (en) * 2019-02-18 2019-06-14 国家计算机网络与信息安全管理中心 Automatic configuration management method and device based on fort machine

Similar Documents

Publication Publication Date Title
CN108667925B (en) Method and system for seamless access of WEB application to distributed system
US9990383B2 (en) Constructing a data adaptor in an enterprise server data ingestion environment
CN109741229B (en) Management system and method applied to rail transit
CN110245030B (en) Data service providing method, device, medium and electronic equipment
CN111858641A (en) Transaction processing method and device, electronic equipment and readable storage medium
CN111324342A (en) Method, device, medium and electronic equipment for generating interface layer code
CN110597602B (en) Transaction processing method and device, computer equipment and storage medium
CN110730197B (en) Service discovery method and system
CN110968433A (en) Information processing method and system and electronic equipment
CN113010561A (en) Data acquisition method and device based on super account book and computer system
CN113220486A (en) Distributed system with separated front and back ends and service calling method, medium and product thereof
CN112202605A (en) Service configuration method, device, equipment and storage medium
WO2018121652A1 (en) Method and device for connecting wireless access point through application in user equipment
CN116302602A (en) Message transmission method and device for mixed development of router protogenesis
CN113691618B (en) Message notification method, device, message center and storage medium
CN111008015B (en) Micro front-end application framework based on front-end technology
CN114925066A (en) Data processing method and device, electronic equipment and storage medium
CN113596164A (en) Data access method, device, system, equipment and medium
CN115292635A (en) Page floor data display method, device, equipment and computer readable medium
CN112929195A (en) Service system, method executed by service system, processing apparatus, and storage medium
CN111414161B (en) Method, device, medium and electronic equipment for generating IDL file
CN114301970A (en) Service calling method and device, electronic equipment and storage medium
CN109669679B (en) Service detection and processing method and device and electronic equipment
CN112905259A (en) Data processing method, device, equipment and storage medium
CN112558941A (en) DDD-based micro-service request processing method, system, device and medium

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