Method for managing configuration of upstream interface

Abstract

The invention relates to the technical field of computers, and discloses a method for configuring and managing an upstream interface, the method is realized through an interface one-key configuration system architecture, and the interface one-key configuration system architecture comprises an interface layer, a service logic layer and a data access layer; the interface layer is configured to be responsible for interacting with a business system and providing a uniform service interface; the business logic layer is configured to process data exchange and conversion between the system and an upstream service and perform business logic processing; and the data access layer is responsible for performing data interaction with an upstream service and providing a data access interface. By the adoption of the method and device, developers can flexibly integrate multiple real name authentication modes into the system through simple configuration operation, upstream interfaces do not need to be in butt joint one by one, the workload of repeated butt joint is reduced, and the stability and development efficiency of the system are improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method for managing upstream interface configuration. Background Art

[0002] With the continuous development and popularization of Internet services, more and more enterprises and organizations need to connect to various upstream services to meet user needs and provide more functions. However, when connecting to different upstream services, they face a common problem: how to manage and configure multiple real-name authentication methods.

[0003] In the prior art, when docking different upstream services, a one-by-one docking method is usually adopted. This is the most direct and traditional method, that is, independent docking work is performed for each upstream service. Developers need to understand the interface specifications and authentication methods of each upstream service and write corresponding code for adaptation. The advantage of this method is that the docking process is more intuitive and the details of each service can be better controlled. However, independent docking and configuration work needs to be performed for each upstream service, which leads to a lot of duplication of work and waste of resources. At the same time, since each upstream service may use different authentication methods and interface specifications, developers need to spend a lot of time and energy to adapt and handle these differences, which brings challenges to the stability and development cycle of the system. Summary of the invention

[0004] The purpose of this application is to provide a method for upstream interface configuration management to solve the technical problems raised in the above background.

[0005] To achieve the above-mentioned purpose, the present application discloses the following technical solutions: a method for upstream interface configuration management, the method is implemented through an interface one-click configuration system architecture, wherein the interface one-click configuration system architecture includes: an interface layer, a business logic layer and a data access layer; the interface layer is configured to: be responsible for interacting with the business system and providing a unified service interface; the business logic layer is configured to: process data exchange and conversion between the system and the upstream service, and perform business logic processing; the data access layer is responsible for data interaction with the upstream service and providing a data access interface.

[0006] Preferably, the method for managing the upstream interface configuration comprises the following steps:

[0007] The front end initiates a request, which is sent to the server;

[0008] The server obtains the call chain and parses the undo parameters and the encapsulation parameters;

[0009] The server sends the request to a third-party server, and the third-party server responds to the request and returns a response data packet to the server;

[0010] The server parses the response parameters based on the received response data packet and returns the required parameters;

[0011] The server sends the request result to the front end.

[0012] Beneficial effect: By adopting the method of upstream interface configuration management of the present application, developers can flexibly integrate multiple real-name authentication methods into the system through simple configuration operations, without having to connect to the upstream interfaces one by one. This not only reduces the workload of repeated connection, but also improves the stability of the system and development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the embodiments of the present application 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 present application. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.

[0014] Figure 1 A schematic diagram of a process flow of a parsing request provided in an embodiment of the present application;

[0015] Figure 2 A flowchart of the execution of the method for upstream interface configuration management provided in an embodiment of the present application. DETAILED DESCRIPTION

[0016] The technical solutions in the embodiments of the present application are described clearly and completely below. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

[0017] In this article, the term "comprising" is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of more restrictions, the elements defined by the sentence "comprising..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0018] The existing one-by-one docking method has the following disadvantages when docking multiple upstream services:

[0019] 1. Large workload: Connecting one by one requires developers to understand the interface specifications and authentication methods of each upstream service and write corresponding code for adaptation. This means that developers need to invest a lot of time and energy to complete each docking task, especially when connecting to multiple services, the workload will increase significantly;

[0020] 2. Time-consuming: Since each docking requires independent work, the entire docking process is very time-consuming. Each docking task requires learning interface specifications, writing and testing codes, etc., all of which take a lot of time;

[0021] 3. Error-prone: In the process of docking one by one, developers need to deal with multiple different service interfaces, each of which may have different parameters, return values ​​and exceptions. This increases the risk of errors. Once a problem occurs, it takes a lot of time and effort to troubleshoot and fix it.

[0022] In this regard, the present embodiment aims to solve the above-mentioned shortcomings of the one-by-one docking method, and to simplify the docking work through a unified interface layer in a configuration manner.

[0023] Specifically, the disclosed method of upstream interface configuration management in this embodiment is implemented through an interface one-click configuration system architecture, which includes: an interface layer, a business logic layer, and a data access layer; the interface layer is configured to: be responsible for interacting with the business system and providing a unified service interface; the business logic layer is configured to: process data exchange and conversion between the system and the upstream service, and perform business logic processing; the data access layer is responsible for data interaction with the upstream service and provides a data access interface. With this architecture, Figure 1 As shown, the method for managing upstream interface configuration specifically includes the following steps:

[0024] The front end initiates a request, which is sent to the server;

[0025] The server obtains the call chain and parses the undo parameters and the encapsulation parameters;

[0026] The server sends the request to a third-party server, and the third-party server responds to the request and returns a response data packet to the server;

[0027] The server parses the response parameters based on the received response data packet and returns the required parameters;

[0028] The server sends the request result to the front end.

[0029] Based on the above, the method for upstream interface configuration management in this embodiment, through encapsulation and unification, developers only need to connect with the configuration system, without having to connect with upstream services one by one, thereby achieving the following purposes:

[0030] 1. Reduce workload: The one-click configuration system can encapsulate and unify the interface specifications and authentication methods of multiple upstream services. Developers only need to connect with the configuration system and do not need to repeat similar work. This will greatly reduce the workload of developers;

[0031] 2. Improve efficiency: By introducing middleware, developers only need to focus on business logic without having to consider the differences in interface specifications and authentication methods. This will improve development efficiency and speed up the system development process;

[0032] 3. Improve stability: The configuration system is responsible for handling the differences between different services and providing a unified interface for the business system to use. This can reduce problems caused by inconsistent interface specifications or different authentication methods and improve system stability;

[0033] 4. By solving the shortcomings of the one-by-one docking method, it aims to improve the efficiency and stability of docking with multiple upstream services, reduce the development workload, and thus promote the development of the entire system.

[0034] The above interface configures the system architecture with one click and has the following features:

[0035] 1. Unification of interface specifications

[0036] The middleware encapsulates and unifies the interface specifications of each upstream service, and provides a standardized interface for the business system to use. In this way, the business system only needs to connect to the standardized interface of the invention system, without having to worry about the differences in the interface specifications and authentication methods of the upstream services. This embodiment uses the OpenAPI specification to define the interface of the middleware to ensure the unification and standardization of the interface;

[0037] 2. Packaging and management of authentication methods

[0038] The middleware encapsulates and unifies the authentication methods of different upstream services to ensure that the business system can correctly call the upstream services. The middleware can support multiple authentication methods, including MD5, SHA1, etc. For upstream services that need to be authenticated, the business system only needs to provide the corresponding authentication information to the middleware, and the middleware will automatically complete the authentication process;

[0039] 3. Unification of exception handling and error codes

[0040] It can handle the abnormal situations returned by the upstream service and provide standardized error codes for the business system to use. The system can map and unify the abnormal situations of different upstream services, thereby avoiding the error handling problems of the business system caused by different error codes.

[0041] Further, the specific execution process of the method for upstream interface configuration management in this embodiment is detailed in Figure 2 shown.

[0042] Based on the above, the method for managing upstream interface configuration in this embodiment has the following technical effects:

[0043] 1. Simplify docking work: By introducing the interface one-click configuration system architecture, the docking work can be simplified. The business system only needs to dock with the standardized interface of the interface one-click configuration system architecture, without having to worry about the differences in interface specifications and authentication methods of upstream services.

[0044] 2. Improve the efficiency of the entire system: The one-click configuration system architecture of the interface can map and unify the abnormal situations of different upstream services, and provide standardized error codes for the business system to use, thereby avoiding problems with error handling in the business system due to different error codes. In addition, the one-click configuration system architecture of the interface can also cache requests, reduce the number of requests to upstream services, and thus improve the efficiency of the entire system.

[0045] 3. Improve system stability: The one-click configuration system architecture adopts cluster deployment to ensure high availability and scalability. The one-click configuration system architecture can automatically expand nodes according to changes in business load, and balance the load of each node through a load balancing algorithm. This can avoid single point failures and improve system stability.

[0046] 4. Increase data security: The one-click configuration system architecture of the interface can encapsulate and unify the authentication methods of various upstream services to ensure that the business system can correctly call upstream services. This can avoid problems such as data leakage caused by improper authentication methods, thereby increasing data security.

[0047] In the embodiments provided in the present application, it should be understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, code or any appropriate combination thereof. For hardware implementation, the processor can be implemented in one or more of the following units: application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), processor, controller, microcontroller, microprocessor, other electronic units designed to implement the functions described herein or their combination. For software implementation, part or all of the flow of the embodiment can be completed by instructing the relevant hardware through a computer program. When implemented, the above program can be stored in a computer-readable storage medium or transmitted as one or more instructions or codes on a computer-readable storage medium. Computer-readable storage media include computer storage media and communication media, wherein the communication medium includes any medium that is convenient for transmitting a computer program from one place to another. The storage medium can be any available medium that a computer can access. The computer-readable storage medium can include but is not limited to RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer.

[0048] It should be noted that, based on the technical solution provided in this embodiment, the following methods are adopted: directly encapsulate the interface specifications and authentication methods of each upstream service in the business system, and handle the abnormal situations and error codes of each service by itself; use the API gateway to encapsulate the interfaces of each upstream service, and provide standardized interfaces for the business system to use. The API gateway can realize functions such as caching and load balancing, thereby improving the efficiency and stability of the entire system; and other alternative solutions, although they can achieve technical effects similar to the technical solution of this embodiment, as mentioned above, this embodiment only proposes the best partial technical implementation examples, therefore, these technical contents implemented based on this embodiment should be within the scope of protection of this application. That is, it should be noted that the above is only a preferred embodiment of this application, and is not used to limit this application. Although the present application is described in detail with reference to the above embodiments, for those skilled in the art, they can still modify the technical solutions recorded in the above embodiments, or replace some of the technical features therein by equivalents. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application should be included in the scope of protection of this application.

Claims

1. A method for upstream interface configuration management, characterized in that: The method is implemented through an interface one-click configuration system architecture, wherein the interface one-click configuration system architecture includes: an interface layer, a business logic layer and a data access layer; the interface layer is configured to be responsible for interacting with the business system and providing a unified service interface; the business logic layer is configured to process data exchange and conversion between the system and the upstream service, and perform business logic processing; the data access layer is responsible for data interaction with the upstream service and provides a data access interface.

2. The method for managing upstream interface configuration according to claim 1, characterized in that: The method for managing upstream interface configuration specifically includes the following steps: The front end initiates a request, which is sent to the server; The server obtains the call chain and parses the undo parameters and the encapsulation parameters; The server sends the request to a third-party server, and the third-party server responds to the request and returns a response data packet to the server; The server parses the response parameters based on the received response data packet and returns the required parameters; The server sends the request result to the front end.

Images