Service distribution system under distributed architecture

Abstract

The embodiment of the invention relates to the technical field of data processing, in particular to a service distribution system under a distributed architecture. According to the scheme, the request message sent by the user is obtained, and the target service is judged and sent to the service filtering component; and the service filtering component screens out the request message of which the target service is the unitized service, determines the routing element information of the request message, and then judges whether the routing element information in the request message is the main routing element or not, so that targeted processing on different routing elements is realized, and the reliability of judging the unit information at the client is improved. According to the method and the system, the request message is sent to the server, then the routing elements are calculated according to a unit number algorithm to obtain unit information corresponding to the request message, and the request message is sent to the corresponding unit in the server according to the unit information to be processed, so that a whole set of complete unitized global routing system is realized, and meanwhile, corresponding efficiency, expandability and usability are considered.

Description

Technical Field

[0001] The embodiments of the present specification relate to the field of data processing technology, and in particular to a business distribution system under a distributed architecture. Background Art

[0002] At present, in order to improve the availability of the system, large-scale distributed systems of enterprises generally adopt unitized architecture for system design and deployment. After the unitized architecture is introduced, data will be stored separately. Therefore, how to support different routing elements in various business scenarios, how to efficiently obtain the service address in one request, cross-unit routing forwarding, intra-unit service convergence, AZ (computer room) service priority, how to efficiently support expansion, hotspot unit data migration, etc. are all issues that need to be considered after unitized splitting.

[0003] At present, operations such as storage, query and maintenance of routing unit information are performed by adding global routing components. Unitized components are added for routing requests and service filtering, and the requests are forwarded to the target service through the underlying communication components to complete the service request and obtain the return result. At the same time, it is considered to add redis cache on the global routing side to cache commonly used information and reduce the time consumption of database query for unit information through routing elements. However, in the prior art, there is no effective distinction between routing element types. For routing element types such as customer number, account number, and ID number, global routing is requested for processing. In actual use, routing elements of customer number type can be directly calculated and processed locally after caching the required information locally, reducing the pressure of global routing and improving response efficiency. At the same time, service types including unitized services and public services can only be distinguished by global routing. It is necessary to carry routing elements to request routing once to distinguish. In fact, the service judgment can be processed in advance through configuration without requesting global routing.

[0004] At present, there is an urgent need for a complete global routing system to achieve efficient, scalable, user-configurable and simple-to-use unitized global routing for financial core systems. Summary of the invention

[0005] In order to solve the problem that the existing technology can only distinguish service types through global routing, and requires carrying routing elements to request a route to distinguish, the embodiment of this specification provides a business distribution system under a distributed architecture, which can perform different processing according to different routing elements to confirm the information of the processing unit; under the unitized architecture, the target service address can be obtained efficiently and quickly, better support system multi-active deployment, complete transaction requests, and improve the scalability and reliability of the system. The specific technical solutions of the embodiment of this specification are as follows:

[0006] On the one hand, the embodiments of this specification provide a service distribution system under a distributed architecture, the system comprising: a client and a server,

[0007] The client includes a unitized component, a service filtering component and a routing forwarding component;

[0008] The unitized component obtains the request message sent by the user, determines the target service of the request message and sends it to the service filtering component;

[0009] The service filtering component obtains the routing element information corresponding to the request message of the unitized service for the target service according to the local cache information, and determines whether the routing element information is a main routing element;

[0010] If the routing element information is a main routing element, the main routing element is calculated according to a preset unit number algorithm to obtain unit information corresponding to the request message;

[0011] If the routing element information is a non-primary routing element, the non-primary routing element is sent to the global routing component of the server to obtain the unit information corresponding to the request message;

[0012] The routing forwarding component sends the request message to the corresponding unit in the server for processing according to the unit information.

[0013] Furthermore, determining the target service of the request message and sending it to the service filtering component further includes:

[0014] Acquire routing element information and service name of the request message according to the request message;

[0015] It is determined whether the target service of the request message is a unitized service according to the relevant routing configuration of the client, the routing element information and the service name.

[0016] Further, determining whether the target service of the request message is a unitized service further includes:

[0017] If the target service of the request message is a unitized service, sending the request message to a service filtering component;

[0018] If the target service of the request message is a non-unitized service, the request message is sent to the non-unitized service component in the server for processing.

[0019] Furthermore, if the routing element information is a main routing element,

[0020] The local cache information also includes unit change information;

[0021] querying the main routing element according to the unit change information;

[0022] If the main routing element is not found in the unit change information, the main routing element is calculated according to a preset unit number algorithm to obtain the unit information corresponding to the request message;

[0023] If the main routing element is found in the unit change information, the request message is sent to the server, and the server determines the unit information corresponding to the request message.

[0024] Furthermore, the service filtering component also includes:

[0025] The unit change information includes unit lock table information, gray unit degree information and unit migration information;

[0026] The server updates the unit change information according to a preset maintenance change plan and sends it to the service filtering component.

[0027] Furthermore, if the routing element information is a non-primary routing element, it further includes:

[0028] Matching is performed in the global routing component to obtain the global routing element associated with the non-primary routing element;

[0029] Calculating the global routing element according to a preset unit number algorithm to obtain unit information corresponding to the request message;

[0030] If the global routing element does not include the non-main routing element, an error processing is performed.

[0031] Furthermore, the routing and forwarding component also includes:

[0032] Filtering the unit list in the server according to the unit information, and obtaining a unit in the unit list that matches the unit information;

[0033] A processing unit is selected according to a preset condition, and the request message is sent to the processing unit for processing.

[0034] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, and the processor implements the above system when executing the computer program.

[0035] On the other hand, an embodiment of the present specification further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above system when executed by a processor.

[0036] Finally, the embodiments of this specification also provide a computer program product, wherein the computer program product includes a computer program, and the computer program implements the above system when executed by a processor.

[0037] By using the embodiments of this specification, a system is provided that can meet the requirements of accurate business allocation under a distributed architecture. The business allocation system in this scheme includes a unitized component, a service filtering component and a routing forwarding component of a client; wherein, the unitized component determines the target service by obtaining the request message sent by the user and sends it to the service filtering component; the service filtering component screens out the request message whose target service is the unitized service, determines its routing element information, and then determines whether the routing element information in the request message is the main routing element, so as to distinguish the routing elements by type, thereby improving the reliability of the client's judgment of the unit information; if the routing element information is a pre-set main routing element, the main routing element can be calculated according to the preset unit number algorithm to obtain the unit information corresponding to the request message; if the routing element information is a non-main routing element, the non-main routing element needs to be sent to the global routing component of the server to obtain the unit information corresponding to the request message; when supporting the addition of new routing element types and table name information in the global routing component, a fast response of zero-code modification of existing routing elements can be achieved. Finally, the routing forwarding component sends the request message to the corresponding unit in the server for processing according to the unit information, realizing a complete unitized global routing system while taking into account the corresponding efficiency, scalability and ease of use. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0039] Figure 1 The figure shows a schematic diagram of an implementation system of a business allocation system under a distributed architecture in an embodiment of this specification;

[0040] Figure 2 The figure shows a result schematic diagram of a business allocation system under a distributed architecture in an embodiment of this specification;

[0041] Figure 3 The figure is a schematic diagram of a process for determining the target service of the request message in an embodiment of the present specification;

[0042] Figure 4The figure is a flow chart of determining whether the target service of the request message is a unitized service in an embodiment of the present specification;

[0043] Figure 5 The figure is a schematic diagram of the process of querying the unit information corresponding to the request message in the embodiment of this specification;

[0044] Figure 6 The figure is a schematic diagram of a process of obtaining the global routing element associated with the non-main routing element in the embodiment of this specification;

[0045] Figure 7 It is a schematic diagram of a process of filtering the unit list in the server in an embodiment of this specification;

[0046] Figure 8 The figure is a schematic diagram of the structure of a computer device in an embodiment of the present specification.

[0047]

Description of the accompanying drawings

[0048] 101. Client;

[0049] 1011, unitized components;

[0050] 1012. Service filtering component;

[0051] 1013. Routing and forwarding component;

[0052] 102. Server;

[0053] 1021. Global routing component;

[0054] 802. Computer equipment;

[0055] 804. Processing equipment;

[0056] 806. Storage resources;

[0057] 808, drive system;

[0058] 810, input / output module;

[0059] 812. Input device;

[0060] 814. Output device;

[0061] 816. Presentation equipment;

[0062] 818. Graphical user interface;

[0063] 820, network interface;

[0064] 822, communication link;

[0065] 824. Communication bus. DETAILED DESCRIPTION

[0066] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the embodiments of this specification.

[0067] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of this specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0068] It should be noted that the acquisition, storage, use, and processing of data in the technical solutions of the embodiments of this specification comply with the relevant provisions of national laws and regulations.

[0069] It should be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0070] like Figure 1 The diagram shows a schematic diagram of an implementation system of a salary calculation result verification method based on a clustering algorithm in an embodiment of the specification, including a client 101 and a server 102. The client 101 and the server 102 can communicate with each other through a network, and the network can include a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof, and is connected to a website, a user device (such as a computing device), and a back-end system. Optionally, the server 102 can be a node of a cloud computing system, or each server can be a separate cloud computing system, including multiple computers interconnected by a network and working as a distributed processing system.

[0071] The client 101 obtains the request message sent by the user, calculates the unit information corresponding to the request message and then sends it to the server 102. The server 102 directly sends the request message to the corresponding unit according to the unit information to process the request message.

[0072] In addition, it should be noted that Figure 1 What is shown is only one application environment provided by the embodiment of this specification. In actual application, other application environments may also be included, and this specification does not limit it.

[0073] In view of the problems existing in the prior art, the embodiments of this specification provide a business distribution system under a distributed architecture, and

[0074] Figure 2 The figure shows a schematic diagram of a business distribution system under a distributed architecture in an embodiment of this specification. The figure describes the working process of the business distribution system under a distributed architecture. The order of steps implemented by the system listed in the embodiment is only one way of executing the order of many steps and does not represent the only execution order. When the system or device product is executed in practice, it can be executed in the order of the method shown in the embodiment or the accompanying drawings or in parallel.

[0075] Specific as Figure 2 As shown, the system includes: a client 101 and a server 102,

[0076] The client 101 includes a unitized component 1011, a service filtering component 1012 and a routing forwarding component 1013;

[0077] The unitization component 1011 obtains the request message sent by the user, determines the target service of the request message and sends it to the service filtering component 1012;

[0078] The service filtering component 1012 obtains the routing element information corresponding to the request message of the target service being a unitized service, and determines whether the routing element information is a main routing element;

[0079] If the routing element information is a main routing element, the main routing element is calculated according to a preset unit number algorithm to obtain unit information corresponding to the request message;

[0080] If the routing element information is a non-main routing element, the non-main routing element is sent to the global routing component 1021 to obtain a global routing element, and the global routing element is calculated according to the unit number algorithm to obtain the unit information corresponding to the request message;

[0081] The routing forwarding component 1013 sends the request message to the corresponding unit in the server 102 for processing according to the unit information.

[0082] By using the embodiments of this specification, a system is provided that can meet the requirements of accurate business allocation under a distributed architecture. The business allocation system in this scheme includes a unitized component, a service filtering component and a routing forwarding component of a client; wherein, the unitized component determines the target service by obtaining the request message sent by the user and sends it to the service filtering component; the service filtering component screens out the request message whose target service is the unitized service, determines its routing element information, and then determines whether the routing element information in the request message is the main routing element, so as to distinguish the routing elements by type, thereby improving the reliability of the client's judgment of the unit information; if the routing element information is a pre-set main routing element, the main routing element can be calculated according to the preset unit number algorithm to obtain the unit information corresponding to the request message; if the routing element information is a non-main routing element, the non-main routing element needs to be sent to the global routing component of the server to obtain the unit information corresponding to the request message; when supporting the addition of new routing element types and table name information in the global routing component, a fast response of zero-code modification of existing routing elements can be achieved. Finally, the routing forwarding component sends the request message to the corresponding unit in the server for processing according to the unit information, realizing a complete unitized global routing system while taking into account the corresponding efficiency, scalability and ease of use.

[0083] In the embodiments of this specification, the existing design cannot effectively distinguish the types of routing elements. For routing element types such as customer number, account number, and certificate number, global routing is requested for processing, which leads to a problem of high pressure on the server. A method of confirming the information of the processing unit by performing different processing according to different routing elements is adopted, so that the routing elements of the customer number type can be directly calculated and processed locally after the required information is cached locally, reducing the pressure of global routing and improving response efficiency. At the same time, under the unitized architecture, the target service address can be obtained efficiently and quickly, better supporting the multi-active deployment of the system, completing transaction requests, and improving the scalability and reliability of the system.

[0084] According to an embodiment of the present specification, in order to determine whether the target service of the request message is a unitized service, the request message can be directly sent to the required unit, such as Figure 3 As shown, determining the target service of the request message and sending it to the service filtering component further includes:

[0085] Step 301: Obtain routing element information and service name of the request message according to the request message;

[0086] Step 302: Determine whether the target service of the request message is a unitized service according to the relevant routing configuration of the client, the routing element information and the service name.

[0087] In the embodiments of this specification, the unitized component 1011 is deployed on the client 101 where the request is initiated, and is mainly responsible for completing the parsing of the client-related routing configuration, obtaining routing elements and specific values, filtering service types, completing global routing requests to obtain unit information, and filtering services by unit after obtaining the unit information. When the client 101 sends a request to the server, the unitized component 1011 will intercept the request, and determine whether it is a request for a non-unit service based on the configuration and the intercepted service name. If it is, it will filter to the target service instance through the configured AZ (computer room) information, and send the request to the server instance. Specifically, by judging whether the target service has a unit tag, it can be judged whether the target service is a unitized service. When filtering the service list, the client will use these unit tags to filter the service results to obtain the required target service.

[0088] According to an embodiment of the present specification, in order to obtain whether the target service of the request message is a unitized service, thereby avoiding cross-service overhead, such as Figure 4 As shown, determining whether the target service of the request message is a unitized service further includes:

[0089] Step 401: If the target service of the request message is a unitized service, the request message is sent to a service filtering component;

[0090] Step 402: If the target service of the request message is a non-unitized service, the request message is sent to the non-unitized service component in the server for processing.

[0091] In the embodiments of the present specification, by distinguishing different types of routing elements, for main routing elements such as customer number classes, the unit number calculation can be performed directly at the initiator. For non-main routing elements, the request message is assembled to request the global routing to obtain the unit information. For the customer number type, the request global routing overhead can be shortened. Among them, each request message type will store its unit, AZ (computer room) and other information when it is first sent to the server, and the unit, AZ (computer room) and other information corresponding to each request type will be stored in the routing forwarding component. After obtaining the unit information and the corresponding AZ information corresponding to the request message, the routing forwarding component filters all instances of the service in the registration center to obtain whether the target service of the request message is a unitized service, thereby reducing the network overhead across AZs (computer rooms).

[0092] According to an embodiment of the present specification, in order to prevent new transactions from occurring during data migration, such as Figure 5As shown, the service filtering component also includes:

[0093] The local cache information also includes unit change information;

[0094] Step 501: querying the main routing element according to the unit change information;

[0095] Step 502: If the main routing element is not found in the unit change information, the main routing element is calculated according to a preset unit number algorithm to obtain the unit information corresponding to the request message;

[0096] Step 503: If the main routing element is found in the unit change information, the request message is sent to the server, and the server determines the unit information corresponding to the request message.

[0097] In the embodiment of this specification, the local cache information contains two caches. First, after obtaining the unit information, it is stored in a map cache through the routing element. If there is the same routing element in the subsequent process of this transaction, the unit information of the cache will be directly used and directly cleared after the transaction ends. Secondly, before performing the unit calculation, it is necessary to first determine whether to lock, migrate units, grayscale, etc. The judgment is to query the three types of data in the cache through the main routing element, that is, the customer number; if it is in the process of hot unit data migration, the user of the migration unit will be locked during migration to prevent new transactions from occurring during the data migration process. After the data migration is completed, the data will be unlocked and new online transactions can continue to be received; therefore, the unit change information is stored in the service filtering component, including the design of the statistical table of routing registration information of each unit, regular scanning statistics, and when the new routing information is registered, the unit number is first calculated according to the algorithm, and the statistical table of each unit information is queried to confirm whether the unit is a hot unit. If not, the calculated unit number is returned. If it is, a non-hot unit is obtained from the unit information statistical table, and the customer number and unit information are registered in the migration unit table for subsequent queries.

[0098] Specifically, the service filtering component also includes:

[0099] The unit change information includes unit lock table information, gray unit degree information and unit migration information;

[0100] The server updates the unit change information according to a preset maintenance change plan and sends it to the service filtering component.

[0101] Exemplarily, if the request is for a unitized service, the routing element information corresponding to the request is first obtained to determine whether it is the main routing element. If so, the locally cached unit lock table information, gray unit degree information, and migration unit information are queried. If the main routing element is not found in any of this information, the main routing element is calculated according to the unit number calculation algorithm to obtain the final unit information returned.

[0102] According to an embodiment of the present specification, in order to complete the allocation of request messages at the client, such as Figure 6 As shown, if the routing element information is a non-primary routing element, it further includes:

[0103] Step 601: performing matching in the global routing component to obtain the global routing element associated with the non-primary routing element;

[0104] Step 602: Calculate the global routing element according to a preset unit number algorithm to obtain unit information corresponding to the request message;

[0105] Step 603: If the global routing element does not contain the non-main routing element, an error is reported. In another embodiment of the present specification, for the global routing component, different types of routing elements are distinguished. Taking the financial scenario as an example, the customer number is selected as the main routing element, and the account number, certificate number, bill number, etc. are selected as non-main routing elements. Among them, the non-main routing element can be dynamically expanded and increased according to the actual business scenario, but all non-main routing elements must be associated with the main routing element. The final unit information needs to be obtained by the main routing element modulus calculation. For the non-main routing element, it is necessary to first obtain the unit information through the associated main routing element modulus calculation and then store it in the association table for subsequent query. Specifically, for the routing query transaction, if the customer number (main routing element) is used, it can be queried directly to confirm that the unit corresponding to the request does not belong to the unit lock table information, gray unit degree information and migration unit migration information. The unit information can be directly obtained according to the unit number modulus. If a non-main routing element is used, it is necessary to query the routing element association table to obtain the associated global routing and unit change information and perform unit information query. If the non-primary routing element cannot be found in the routing element association table, it means that the information is wrong or the customer does not exist, so an error notification is issued for manual processing.

[0106] According to one embodiment of this specification, Figure 7 As shown, the routing forwarding component also includes:

[0107] Step 701: filtering the unit list in the server according to the unit information, and obtaining at least one unit in the unit list that matches the unit information;

[0108] Step 702: Select a processing unit according to preset conditions, and send the request message to the processing unit for processing.

[0109] In another embodiment of the present specification, the local database of the server stores and maintains parameter data, and when the data changes, the configuration center is notified of the parameter change. After receiving the change notification from the configuration center, the client calls the parameter query interface, pulls the changed parameter information from the server, parses it locally and puts it into the cache, and generates preset conditions based on the parameter information, thereby ensuring that the client can query the local memory when using the data, and can send the request message to the appropriate processing unit for processing, thereby improving the efficiency of request processing.

[0110] In the embodiments of the present specification, a global routing system is designed under a complete unitized mechanism to support multiple routing elements and distinguish between routing element types. The main routing elements such as customer numbers are directly calculated by the client, and other routing elements access the global routing to obtain routing information. The judgment of the service type is realized through configuration in advance to avoid useless network access, improve query efficiency, and reduce global routing pressure. And through the routing service forwarding component, useless cross-unit network overhead is avoided, and service degradation and priority access to the nearest AZ (computer room) are supported.

[0111] like Figure 8 The figure is a schematic diagram of the structure of a computer device according to an embodiment of the present specification. The computer device according to the embodiment of the present specification can run the method according to the embodiment of the present specification.

[0112] The computer device 802 may include one or more processing devices 804, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 802 may also include any storage resources 806 for storing any type of information such as code, settings, data, etc. Without limitation, for example, the storage resources 806 may include any one or more combinations of the following: any type of RAM, any type of ROM, a flash memory device, a hard disk, an optical disk, etc. More generally, any storage resource may use any technology to store information.

[0113] Further, any storage resource may provide volatile or non-volatile retention of information.

[0114] Further, any storage resource may represent a fixed or removable component of the computer device 802. In one case, when the processing device 804 executes the associated instructions stored in any storage resource or combination of storage resources, the computer device 802 may perform any operation of the associated instructions. The computer device 802 also includes one or more drive systems 808 for interacting with any storage resource, such as a hard disk drive system, an optical disk drive system, etc.

[0115] The computer device 802 may also include an input / output module 810 (I / O) for receiving various inputs (via input devices 812) and for providing various outputs (via output devices 814). A specific output mechanism may include a presentation device 816 and an associated graphical user interface 818 (GUI). In other embodiments, the input / output module 810 (I / O), input device 812, and output device 814 may not be included, and the computer device 802 may be used as a computer device in a network. The computer device 802 may also include one or more network interfaces 820 for exchanging data with other devices via one or more communication links 822. One or more communication buses 824 couple the components described above together.

[0116] The communication link 822 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 822 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0117] The embodiments of the present specification also provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0118] The embodiments of the present specification also provide a computer-readable instruction, wherein when a processor executes the instruction, the program therein causes the processor to execute the above method.

[0119] It should be understood that in the various embodiments of the present specification, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present specification.

[0120] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in the embodiments of this specification generally indicates that the associated objects before and after are in an "or" relationship.

[0121] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of this specification can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of this specification.

[0122] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0123] In the several embodiments provided in the embodiments of this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0124] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this specification.

[0125] In addition, each functional unit in each embodiment of the present specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0126] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of this specification is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the embodiment of this specification. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0127] The embodiments of this specification use specific embodiments to illustrate the principles and implementation methods of the embodiments of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of the embodiments of this specification. At the same time, for those skilled in the art, according to the ideas of the embodiments of this specification, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the embodiments of this specification.

Claims

1. A business distribution system under a distributed architecture, characterized in that: The system comprises: a client and a server, The client includes a unitized component, a service filtering component and a routing forwarding component; The unitized component obtains the request message sent by the user, determines the target service of the request message and sends it to the service filtering component; The service filtering component obtains the routing element information corresponding to the request message of the unitized service for the target service according to the local cache information, and determines whether the routing element information is a main routing element; If the routing element information is a main routing element, the main routing element is calculated according to a preset unit number algorithm to obtain unit information corresponding to the request message; If the routing element information is a non-primary routing element, the non-primary routing element is sent to the global routing component of the server to obtain the unit information corresponding to the request message; The routing forwarding component sends the request message to the corresponding unit in the server for processing according to the unit information.

2. The service distribution system under the distributed architecture according to claim 1, characterized in that: Determining the target service of the request message and sending it to the service filtering component further includes: Acquire routing element information and service name of the request message according to the request message; It is determined whether the target service of the request message is a unitized service according to the relevant routing configuration of the client, the routing element information and the service name.

3. The business distribution system under the distributed architecture according to claim 2 is characterized in that: Determining whether the target service of the request message is a unitized service further includes: If the target service of the request message is a unitized service, sending the request message to a service filtering component; If the target service of the request message is a non-unitized service, the request message is sent to the non-unitized service component in the server for processing.

4. The business distribution system under the distributed architecture according to claim 1, characterized in that: If the routing element information is a main routing element, it also includes: The local cache information also includes unit change information; querying the main routing element according to the unit change information; If the main routing element is not found in the unit change information, the main routing element is calculated according to a preset unit number algorithm to obtain the unit information corresponding to the request message; If the main routing element is found in the unit change information, the request message is sent to the server, and the server determines the unit information corresponding to the request message.

5. The business distribution system under the distributed architecture according to claim 4, characterized in that: The service filtering component also includes: The unit change information includes unit lock table information, gray unit degree information and unit migration information; The server updates the unit change information according to a preset maintenance change plan and sends it to the service filtering component.

6. The business distribution system under the distributed architecture according to claim 1, characterized in that: If the routing element information is a non-primary routing element, it further includes: Matching is performed in the global routing component to obtain the global routing element associated with the non-primary routing element; Calculating the global routing element according to a preset unit number algorithm to obtain unit information corresponding to the request message; If the global routing element does not include the non-main routing element, an error processing is performed.

7. The business distribution system under the distributed architecture according to claim 1, characterized in that: The routing and forwarding component also includes: Filtering the unit list in the server according to the unit information, and obtaining a unit in the unit list that matches the unit information; A processing unit is selected according to a preset condition, and the request message is sent to the processing unit for processing.

8. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the processor executes the computer program, the system according to any one of claims 1 to 7 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the system according to any one of claims 1 to 7 is implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the system according to any one of claims 1 to 7 is implemented.

Images