CN109194760A - Method for processing business, network system and server - Google Patents
Method for processing business, network system and server Download PDFInfo
- Publication number
- CN109194760A CN109194760A CN201811083701.0A CN201811083701A CN109194760A CN 109194760 A CN109194760 A CN 109194760A CN 201811083701 A CN201811083701 A CN 201811083701A CN 109194760 A CN109194760 A CN 109194760A
- Authority
- CN
- China
- Prior art keywords
- service
- target
- request
- target service
- api gateway
- 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.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the present invention provides a kind of method for processing business, network system and server, wherein network system includes API gateway, operation system and operational support system, OSS, the operation system includes at least one business micro services component, and the operational support system, OSS includes configuration center；The described method includes: the API gateway receives the service request that client is sent, the configuration information of the target service is obtained from the configuration center of the operational support system, OSS according to the mark of requested target service；Determine whether the requestor has the request permissions of the target service according to the configuration information of the target service；If having, the business micro services component in the operation system is called to be handled the target service to respond the service request.The present invention is capable of handling polymorphic type business, guarantees the stability and reliability of network system.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a service processing method, a network system, and a server.
Background
The existing service processing procedure is usually that a client initiates a service request to a network system side, and the network system performs service processing to respond to the service request. However, in practice, it is found that in the service processing process of the existing network system, various service requests need to be transmitted to the network system through different interfaces, which increases the development and maintenance overhead of the system, and requires that a user must clearly know the corresponding relationship between various service requests and the interfaces, otherwise, the service requests cannot be transmitted through the correct interfaces, so that the smooth execution of the service processing process cannot be guaranteed, and the security and reliability of the network system cannot be guaranteed.
Disclosure of Invention
Embodiments of the present invention provide a service processing method, a network system, and a server, which can ensure smooth execution of various service processing procedures and ensure stability and reliability of the network system.
On one hand, the embodiment of the present invention provides a service processing method, which is applied to a network system, where the network system is provided with a cellular framework, and the cellular framework is configured by using a spring cloud (ordered set of a series of frameworks); the network system comprises an API (Application Programming Interface) gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; the method comprises the following steps:
the API gateway receives a service request sent by a client, wherein the service request carries a requester identifier and a requested target service identifier;
the API gateway acquires configuration information of the target service from a configuration center of the operation support system according to the identification of the target service, wherein the configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identification allowing the request of the target service;
the API gateway determines whether the requester has the request permission of the target service according to the configuration information of the target service;
if yes, the API gateway calls a service micro-service component in the service system to process the target service so as to respond to the service request.
In another aspect, an embodiment of the present invention provides a network system, where the network system includes a cellular framework, and the cellular framework is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; wherein,
the service micro-service component is used for carrying out service processing; the configuration center is at least used for managing configuration information of a target service, the configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identifier allowing the request of the target service;
the API gateway is used for receiving a service request sent by a client, wherein the service request carries a requester identifier and a requested target service identifier; acquiring configuration information of the target service from a configuration center of the operation support system according to the identifier of the target service; determining whether the requester has the request authority of the target service according to the configuration information of the target service; and if so, calling a service microservice component in the service system to process the target service so as to respond to the service request.
In another aspect, an embodiment of the present invention provides a service processing server, including:
a computer storage medium storing a network system, the network system being provided with a cellular architecture, the cellular architecture being configured with a SpringCloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center;
a processor adapted to load the network system in the computer storage medium to perform the following method:
receiving a service request sent by a client by the API gateway in the network system, wherein the service request carries an identifier of a requester and an identifier of a requested target service;
the API gateway acquires configuration information of the target service from a configuration center of the operation support system according to the identification of the target service, wherein the configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identification allowing the request of the target service;
the API gateway determines whether the requester has the request permission of the target service according to the configuration information of the target service;
if yes, the API gateway calls a service micro-service component in the service system to process the target service so as to respond to the service request.
The network system of the embodiment of the invention is provided with a honeycomb framework, and the honeycomb framework is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; further, when receiving a service request sent by a client, the API gateway acquires configuration information of a requested target service from a configuration center of the operation support system; determining whether the requester has the request authority of the target service according to the configuration information of the target service; calling a business microservice component in the business system to process the target business to respond to the business request when determining that the business microservice component has the request permission; it can be seen that the API gateway is set to interact with the client, which is equivalent to transmitting various service requests to the network system for processing by using a uniform interface, and the user at the client side does not need to distinguish the corresponding relationship between the type of the service request and various interfaces, so that the service processing process is prevented from being affected by an interface error, which is beneficial to the smooth execution of various service processing processes.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Wherein:
fig. 1 is a schematic structural diagram of a conventional network system;
fig. 2 is a schematic structural diagram of a network system according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of an embodiment of a service processing method according to the present invention;
fig. 4 is a schematic flowchart of another embodiment of a service processing method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a service processing server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, a cellular architecture included in a conventional network system is a set of distributed architectures implemented by configuring a Dubbo (open source distributed service framework) by using SpringMVC (a Java language-based development framework), which includes a database, a Dubbo framework, a business service component, an access interface, and the like. The database is used for storing various data in the network system, including configuration information of business processing, archive files of the business processing and the like; the Dubbo module is an open source distributed service framework and is used for connecting the service components and the service interfaces, so that a user can access the corresponding service components through the service interfaces; the business components are classified according to different businesses and are used for providing different business services; the access interface is used for receiving a service request of a client and is connected with the service assembly through the Dubbo module. The network system shown in fig. 1 operates as follows: the client learns the corresponding relationship between the type of the service request and the access interface from the network system, for example: setting an access interface 1 corresponding to an uploading service and an access interface 2 corresponding to a downloading service; then, when the user has an upload service requirement, the client needs to send an upload service request to the access interface 1; when the user has a downloading service requirement, the client needs to send a downloading service request to the access interface 2; the access interface transmits the corresponding service request to the Dubbo module, the Dubbo module calls a service component corresponding to the requested service type to perform service processing, the service component can call required data from the database in the service processing process, and the processed result data can also be stored in the database. Practice shows that in the network system shown in fig. 1, since the service requests are accessed through the corresponding proprietary interfaces, when the number of service requests increases, the corresponding access interfaces need to be increased, which increases the system overhead and makes the framework of the network system increase continuously, which is not favorable for maintenance; secondly, the user must know the corresponding relationship between the type of the service request and the access interface, otherwise, the service request cannot be transmitted through the correct interface, so that the smooth execution of the service processing process cannot be guaranteed, and the security and reliability of the network system cannot be guaranteed.
In this regard, embodiments of the present invention provide a network system, which is also provided with a cellular architecture, but the cellular architecture adopts a spring cloud framework configuration. Referring to fig. 2, the network system includes: the network system comprises an API gateway 201, a service system 202 and an operation support system 203; optionally, the network system may further include: a service monitoring system 204 and a log management system 205; the business system comprises at least one business micro-service component (such as business micro-service component 1, business micro-service component 2 … … business micro-service component n shown in fig. 2), the operation support system comprises a configuration center, and optionally, the operation support system also comprises a registration center; wherein,
the business microserver component is used for business processing, and can be a piece of computer code used for executing business processing; different from the business component shown in fig. 1, the business component mainly provides services for a single application, and the business micro-service component can divide the single application into a group of micro-services, so that more diversified and more refined business services can be provided as required. The configuration center is at least used for managing configuration information of the target service, the configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identification allowing the request of the target service. The registry is used for managing a plurality of registered users in the network system and user information of each registered user, wherein the user information can comprise registration information, login state, login information and the like.
The API gateway is used for receiving a service request sent by a client, wherein the service request carries a requester identifier and a requested target service identifier; acquiring configuration information of the target service from a configuration center of the operation support system according to the identifier of the target service; determining whether the requester has the request authority of the target service according to the configuration information of the target service; and if so, calling a service microservice component in the service system to process the target service so as to respond to the service request.
The service monitoring system comprises a micro-service state query unit, a distributed tracking unit and the like, and is used for monitoring the service processing process of the target service, generating a log and uploading the log to the log management system. And the log management system is used for receiving and storing the log uploaded by the service monitoring system.
The operation of the network system shown in fig. 2 will be described in detail with reference to an embodiment of the service processing method shown in fig. 3. Referring to fig. 3, this embodiment specifically includes the following steps s301 to s 304:
and s301, the API gateway receiving a service request sent by the client, where the service request carries the identifier of the requester and the identifier of the requested target service.
The service request may include, but is not limited to, a file upload request, a file download request, a gray scale publication request, and the like. The requester identifier may include an ID (Identity) of the user, an IP (Internet Protocol) address of the client, and the like, and is used for uniquely identifying a requester; the identification of the requested target service is used to identify the requested target service. An identifier of a requested target service corresponds to a service, for example, if the identifier of the target service is 001, the target service is a file upload service; if the identification of the target service is 002, the target service is a file downloading service; and if the identification of the target service is 003, the target service is a gray release service. In step s301, a user may initiate a service access through a client, in a specific implementation, the client may be a device such as a mobile phone and a tablet computer, a service APP (application) may be installed in the terminal, and the user runs the service APP and initiates a service request in an interactive interface of the service APP; the service request includes an identification of the requestor and an identification of the requested target service.
s302, the API gateway obtains configuration information of the target service from a configuration center of the operation support system according to the identifier of the target service, where the configuration information includes a user list allowing the request of the target service, and the user list includes at least one user identifier allowing the request of the target service.
The configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identifier allowing the request of the target service and is used for judging whether the requester identifier is consistent with the user identifiers in the user list. The identifier of each target service and the corresponding user list are stored in a database in advance, and query is performed according to the identifier of the target service, for example, if the identifier of the target service is 003, the user list allowing to request the target service is an IP address including 192.168.1.X to 192.168.223. X. The configuration information further includes a service micro-component corresponding to the identifier of the target service for executing the target service, and the identifier of one target service corresponds to one service micro-component for executing the target service, and is stored in a database in advance, for example, if the identifier of the target service is 001, the first service micro-component for uploading a file is used for executing the target service; if the identification of the target service is 002, executing the target service is a second service micro-service component for file downloading processing; and if the identifier of the target service is 003, executing a third service micro-service component for performing gray release processing on the target service, wherein the number of the third service micro-service components corresponds to the version information of the target service one by one.
And s303, the API gateway determines whether the visitor has the request permission of the target service according to the configuration information of the target service.
And judging whether the requester has the request authority of the target service, and judging whether a service system responds to the service request of the requester. The API gateway sends query information carrying the requester identifier to a configuration center, queries whether the requester identifier belongs to the user identifier in the user list, and if so, determines that the requester has the request permission of the target service; if not, determining that the requester does not have the request permission of the target service. For example, the configuration information of the target service includes that the list of users allowed to request the target service is IP addresses including 192.168.1.X to 192.168.223.X, and the IP address of the requester is 192.168.1.168, then the requester identifier belongs to the user identifier in the user list, and it is determined that the requester has the request right of the target service.
And s304, if so, the API gateway calls the service micro-service component in the service system to process the target service so as to respond to the service request.
The service system responds to the service request to ensure that the service processing process is smoothly executed. According to the above content, if the service request permission passes the verification, the API gateway calls a service microservice component to process the service request according to the identifier of the target service. Specifically, different service requests invoke different service micro-service components according to different target service identifiers, for example, if the target service identifier is 003, the third service micro-service component for performing the gray scale publishing process is invoked to execute the gray scale publishing service.
In the embodiment of the invention, the network system is provided with a honeycomb framework, and the honeycomb framework is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; further, when receiving a service request sent by a client, the API gateway acquires configuration information of a requested target service from a configuration center of the operation support system; determining whether the requester has the request authority of the target service according to the configuration information of the target service; calling a business microservice component in the business system to process the target business to respond to the business request when determining that the business microservice component has the request permission; it can be seen that the API gateway is set to interact with the client, which is equivalent to transmitting various service requests to the network system for processing by using a uniform interface, and the user at the client side does not need to distinguish the corresponding relationship between the type of the service request and various interfaces, so that the service processing process is prevented from being affected by an interface error, which is beneficial to the smooth execution of various service processing processes.
The operation of the network system shown in fig. 2 will be described in detail with reference to another embodiment of the service processing method shown in fig. 4. Referring to fig. 4, this embodiment specifically includes the following steps s401-s 406:
and s401, the API gateway receives a service request sent by the client, wherein the service request carries the identifier of the requester and the identifier of the requested target service. Step s401 of this embodiment can refer to step s301 shown in fig. 3, which is not described herein.
s402, the API gateway sends a query request to a registry in the operation support system, where the query request carries the requestor identifier;
in a specific implementation, step s402 may include the following steps:
a1, the registration center inquires whether the requester is a registered user of the network system according to the inquiry request, and inquires whether the requester has successfully logged in;
a2, if the user is not registered, the registration center returns the registration state of the requester to the API gateway and sends registration prompt information to the API gateway;
a3, if the user is a registered user and the login is successful, the registry returns the registration state and the login state of the requester to the API gateway;
a4, if the user is a registered user but the login is not successful, the registration center returns the registration state of the requester to the API gateway and sends login prompt information to the API gateway;
before the API gateway obtains the configuration information of the target service from the configuration center of the operation support system according to the identifier of the target service, it needs to first determine whether the requester is a registered user of the network system or whether the requester has logged in the network system, so as to ensure that the authorization verification of the subsequent service request can be performed smoothly. The registration center presets and stores a registered user list, and updates the registered user list when a new user is registered. In a specific implementation, the registry queries whether the requester belongs to a registered user of the network system according to the requester identifier, and if so, determines that the requester is the registered user; if not, determining that the requester is an illegal user, and sending an access refusal message to the API gateway. The requester is determined to be a registered user, the registry inquires whether the requester successfully logs in according to the requester identifier, if so, the session user is saved, and a token is returned; if the login is not successful, login prompt information is sent to the API gateway to remind a requester to log in the network system.
S403, the API gateway obtains configuration information of the target service from a configuration center of the operation support system according to the identifier of the target service, wherein the configuration information includes a user list allowing the request of the target service, and the user list includes at least one user identifier allowing the request of the target service. Step s403 of this embodiment can refer to step s303 shown in fig. 3, which is not described herein.
S404, the API gateway determines whether the requester has the request authority of the target service according to the configuration information of the target service.
And judging whether the requester has the request authority of the target service according to the configuration information of the target service, and judging whether a service system responds to the service request of the requester. According to step s402, the API gateway determines whether the requestor is a registered user and has successfully logged in to the system, and if the requestor is a registered user and has successfully logged in to the system, the token is carried by the identifier of the requestor. Further, the API gateway sends query information carrying the requester identifier to a configuration center, queries whether the requester identifier belongs to the user identifier in the user list, determines that the requester has the request permission of the target service if the requester identifier belongs to the user identifier in the user list, generates token to cookie, and returns configuration information to the API gateway; if not, determining that the requester does not have the request permission of the target service, and sending a request rejection message to the API gateway. For example, the configuration information of the target service includes that a user list allowing to request the target service is an IP address including 192.168.1.X to 192.168.223.X, and the IP address of the requester is 192.168.1.168, so that the requester identifier belongs to the user identifier in the user list, the requester is determined to have the request right of the target service, a token is generated to a cookie, and configuration information is returned to the API gateway; if the requester identifier is that the IP address of the user is 192.172.1.168, the requester identifier does not belong to the user identifier in the user list, the requester is determined not to have the request permission of the target service, and a request rejection message is sent to the API gateway.
S405, if yes, the API gateway calls a service micro-service component in the service system to process the target service so as to respond to the service request.
The service system responds to the service request to ensure that the service processing process is smoothly executed. According to the above content, if the service request permission passes the verification, the API gateway calls a service microservice component to process the service request according to the identifier of the target service. In a specific implementation, step s405 may include the following steps:
b1, the API gateway inquires the corresponding service micro service component in the service system according to the identification of the target service;
b2, the API gateway calls the corresponding business micro service component in the business system to respond the business request.
In a feasible implementation manner, if the target service is a file upload service, the identifier of the target service is 001, and the corresponding service micro-service component in the service system is a first service micro-service component for file upload processing. And the API gateway calls the first service micro-service component to execute the file uploading service.
In another possible implementation manner, if the target service is a file download service, the identifier of the target service is 002, and the corresponding service micro-service component in the service system is a second service micro-service component for file upload processing. And the API gateway calls the second service micro-service component to execute the file downloading service.
In another possible implementation manner, if the target service is a gray release service, the identifier of the target service is 003, the corresponding service microservice component in the service system is a third service microservice component for performing gray release processing, and the number of the third service microservice components corresponds to the version information of the target service one to one. If the target service is a gray release service, and since the gray release service needs to further determine whether the current version information of the target service is consistent with the target version information, to determine which third service micro-service component is used to execute the gray release service, step b2 further includes:
the API gateway acquires the current version information about the target service in the client;
the API gateway judges whether service upgrading is needed according to the current version information of the target service and the configuration information;
if the current version information of the target service is inconsistent with the target version information, service upgrading is required, and the API gateway calls a third service micro-service component corresponding to the target version information to process the target service so as to respond to the service request;
if the current version information of the target service is consistent with the target version information, service upgrading is not needed, and the API gateway calls a third service micro-service component corresponding to the current version information to process the target service so as to respond to the service request.
According to the above steps, since the third service micro service components correspond to the version information of the target service one to one, according to the identifier of the target service, the current version information of the target service and the target version information, it can be determined which third service micro service component is selected to execute the gray release service, and a service processing flow is completed.
And s406, the service monitoring system monitors the service processing process of the target service and generates a log, and the log is uploaded to the log management system for storage management.
In a possible implementation manner, when receiving a log query request sent by the client, the API gateway forwards the log query request to the log management system; and the log management system returns the log requested to be inquired to the API gateway, and the API gateway outputs the returned log to the client.
In the embodiment of the invention, the network system is provided with a honeycomb framework, and the honeycomb framework is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; further, when the API gateway receives a service request sent by a client, the API gateway acquires registration information and login information of the service request from a registration center in the operation support system; acquiring configuration information of the requested target service from a configuration center of the operation support system; determining whether the requester has the request authority of the target service according to the configuration information of the target service; calling a business microservice component in the business system to process the target business to respond to the business request when determining that the business microservice component has the request permission; the service monitoring system monitors the service processing process of the target service, generates a log, and uploads the log to the log management system for storage management; it can be seen that the API gateway is set to interact with the client, which is equivalent to transmitting various service requests to the network system for processing by using a uniform interface, and the user at the client side does not need to distinguish the corresponding relationship between the type of the service request and various interfaces, so that the service processing process is prevented from being affected by an interface error, which is beneficial to the smooth execution of various service processing processes.
Based on the description of the embodiments of the network system and the service processing method, an embodiment of the present invention further provides a service processing server, which can be loaded into the network system and applied to the service processing methods shown in fig. 3 and fig. 4, so as to execute corresponding steps in the service processing methods. Referring to fig. 5, the internal structure of the server may include a processor, a network interface and a computer storage medium, which may be connected by a bus or other means, and fig. 4 illustrates an example of the connection by the bus according to the embodiment of the present invention.
The communication interface is a medium for realizing interaction and information exchange between the server and the external device. The processor (or CPU) is a computing core and a control core of the server, and is adapted to implement one or more instructions, and in particular, is adapted to load and execute one or more instructions to implement corresponding method flows or corresponding functions; a computer storage medium (Memory) is a Memory device in a server for storing programs and data. It is understood that the computer storage medium herein may include both the built-in storage medium of the server and, of course, the extended storage medium supported by the server. The computer storage media provides storage space that stores the operating system of the server. Also, one or more instructions, which may be one or more computer programs (including program code), are stored in the memory space and are adapted to be loaded and executed by the processor. It should be noted that the computer storage medium may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), such as at least one disk memory; and optionally at least one computer storage medium located remotely from the processor.
In one embodiment, the computer storage medium stores a network system, the network system is provided with a cellular architecture, and the cellular architecture is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; the processor is adapted to load the network system in the computer storage medium, and the relevant device in the network system can execute the corresponding steps in the method flows shown in fig. 3 and 4; in a specific implementation, the processor loads the network system, and the related devices in the network system execute the following steps:
the API gateway receives a service request sent by a client, wherein the service request carries a requester identifier and a requested target service identifier;
the API gateway acquires configuration information of the target service from a configuration center of the operation support system according to the identification of the target service, wherein the configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identification allowing the request of the target service;
the API gateway determines whether the requester has the request permission of the target service according to the configuration information of the target service;
if yes, the API gateway calls a service micro-service component in the service system to process the target service so as to respond to the service request.
In one embodiment, before the processor loads the network system and the API gateway in the network system determines whether the requestor has the request right of the target service according to the configuration information of the target service, the method further includes:
the API gateway sends a query request to a registration center in the operation support system, wherein the query request carries the requester identifier;
the registry inquires whether the requester is a registered user of the network system according to the inquiry request and inquires whether the requester is successfully logged in;
the registry returns the registration state and the login state of the requester to the API gateway;
and if the requester is a registered user and successfully logs in, the API gateway executes a step of determining whether the requester has the request permission of the target service according to the configuration information of the target service.
In another embodiment, the loading the network system, and the determining, by the API gateway in the network system, whether the requester has the request permission of the target service according to the configuration information of the target service specifically includes:
the API gateway judges whether the requester identifier belongs to the user identifier in the user list;
and if the service belongs to the target service, the requester has the request permission of the target service.
In yet another embodiment, the target service includes any one of: a file uploading service, a file downloading service or a gray release service;
if the target service is a file uploading service, the service system comprises at least one first service micro-service component for file uploading processing;
if the target service is a file downloading service, the service system comprises at least one second service micro-service component for file downloading processing;
if the target service is a gray release service, the service system comprises at least one third service micro-service component for performing gray release processing, and the number of the third service micro-service components corresponds to the version information of the target service one by one.
In another embodiment, if the target service is a gray release service, the configuration information further includes target version information of the target service to be released and a release object identifier set of the target version information; the processor loads the network system, and the API gateway in the network system calls a service microservice component in the service system to process the target service to respond to the service request, specifically including:
the API gateway acquires the current version information about the target service in the client;
the API gateway judges whether service upgrading is needed according to the current version information of the target service and the configuration information;
if the service is required to be upgraded, the API gateway calls a third service micro-service component corresponding to the target version information to process the target service so as to respond to the service request;
and if the service upgrading is not needed, the API gateway calls a third service micro-service component corresponding to the current version information to process the target service so as to respond to the service request.
In another embodiment, the processor loads the network system, and the service monitoring system in the network system performs the following steps:
monitoring the service processing process of the target service and generating a log;
and uploading the log to the log management system for storage management.
In still another embodiment, the processor loads the network system, and the related devices in the network system perform the following steps:
when receiving a log query request sent by the client, the API gateway forwards the log query request to the log management system;
and the log management system returns the log requested to be inquired to the API gateway, and the API gateway outputs the returned log to the client.
In the embodiment of the invention, the network system is provided with a honeycomb framework, and the honeycomb framework is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; further, when receiving a service request sent by a client, the API gateway acquires configuration information of a requested target service from a configuration center of the operation support system; determining whether the requester has the request authority of the target service according to the configuration information of the target service; calling a business microservice component in the business system to process the target business to respond to the business request when determining that the business microservice component has the request permission; it can be seen that the API gateway is set to interact with the client, which is equivalent to transmitting various service requests to the network system for processing by using a uniform interface, and the user at the client side does not need to distinguish the corresponding relationship between the type of the service request and various interfaces, so that the service processing process is prevented from being affected by an interface error, which is beneficial to the smooth execution of various service processing processes.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.
Claims (10)
1. A service processing method is applied to a network system, and is characterized in that the network system is provided with a honeycomb framework, and the honeycomb framework is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; the method comprises the following steps:
the API gateway receives a service request sent by a client, wherein the service request carries a requester identifier and a requested target service identifier;
the API gateway acquires configuration information of the target service from a configuration center of the operation support system according to the identification of the target service, wherein the configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identification allowing the request of the target service;
the API gateway determines whether the requester has the request permission of the target service according to the configuration information of the target service;
if yes, the API gateway calls a service micro-service component in the service system to process the target service so as to respond to the service request.
2. The method of claim 1, wherein the operational support system further comprises a registry;
before the API gateway determines whether the requester has the request permission of the target service according to the configuration information of the target service, the API gateway further includes:
the API gateway sends a query request to a registration center in the operation support system, wherein the query request carries the requester identifier;
the registry inquires whether the requester is a registered user of the network system according to the inquiry request and inquires whether the requester is successfully logged in;
the registry returns the registration state and the login state of the requester to the API gateway;
and if the requester is a registered user and successfully logs in, the API gateway executes a step of determining whether the requester has the request permission of the target service according to the configuration information of the target service.
3. The method of claim 1 or 2, wherein the determining, by the API gateway according to the configuration information of the target service, whether the requestor has the request right of the target service comprises:
the API gateway judges whether the requester identifier belongs to the user identifier in the user list;
and if the service belongs to the target service, the requester has the request permission of the target service.
4. A method according to any of claims 1-3, wherein the target service comprises any of: a file uploading service, a file downloading service or a gray release service;
if the target service is a file uploading service, the service system comprises at least one first service micro-service component for file uploading processing;
if the target service is a file downloading service, the service system comprises at least one second service micro-service component for file downloading processing;
if the target service is a gray release service, the service system comprises at least one third service micro-service component for performing gray release processing, and the number of the third service micro-service components corresponds to the version information of the target service one by one.
5. The method according to claim 4, wherein if the target service is a gray release service, the configuration information further includes target version information of the target service to be released and a release object identifier set of the target version information;
the API gateway calls a service micro-service component in the service system to process the target service so as to respond to the service request, and the method comprises the following steps:
the API gateway acquires the current version information about the target service in the client;
the API gateway judges whether service upgrading is needed according to the current version information of the target service and the configuration information;
if the service is required to be upgraded, the API gateway calls a third service micro-service component corresponding to the target version information to process the target service so as to respond to the service request;
and if the service upgrading is not needed, the API gateway calls a third service micro-service component corresponding to the current version information to process the target service so as to respond to the service request.
6. The method of claim 5, wherein the determining, by the API gateway according to the current version information of the target service and the configuration information, whether a service upgrade is required comprises:
the API gateway judges whether the current version information is consistent with the target version information;
if not, the API gateway determines that service upgrading is needed;
and if so, determining that the service upgrading is not needed by the API gateway.
7. The method of claim 1, wherein the network system further comprises a service monitoring system and a log management system, the method further comprising:
the service monitoring system monitors the service processing process of the target service and generates a log;
and the service monitoring system uploads the log to the log management system for storage management.
8. The method of claim 7, further comprising:
when receiving a log query request sent by the client, the API gateway forwards the log query request to the log management system;
and the log management system returns the log requested to be inquired to the API gateway, and the API gateway outputs the returned log to the client.
9. A network system is characterized in that the network system is provided with a honeycomb framework, and the honeycomb framework is configured by a spring cloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center; wherein,
the service micro-service component is used for carrying out service processing; the configuration center is at least used for managing configuration information of a target service, the configuration information comprises a user list allowing the request of the target service, and the user list comprises at least one user identifier allowing the request of the target service;
the API gateway is used for receiving a service request sent by a client, wherein the service request carries a requester identifier and a requested target service identifier; acquiring configuration information of the target service from a configuration center of the operation support system according to the identifier of the target service; determining whether the requester has the request authority of the target service according to the configuration information of the target service; and if so, calling a service microservice component in the service system to process the target service so as to respond to the service request.
10. A transaction server, comprising:
a computer storage medium storing a network system, the network system being provided with a cellular architecture, the cellular architecture being configured with a SpringCloud framework; the network system comprises an API gateway, a service system and an operation support system, wherein the service system comprises at least one service micro-service component, and the operation support system comprises a configuration center;
a processor adapted to load a network system in the computer storage medium to perform the traffic processing method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811083701.0A CN109194760A (en) | 2018-09-14 | 2018-09-14 | Method for processing business, network system and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811083701.0A CN109194760A (en) | 2018-09-14 | 2018-09-14 | Method for processing business, network system and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109194760A true CN109194760A (en) | 2019-01-11 |
Family
ID=64911927
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811083701.0A Withdrawn CN109194760A (en) | 2018-09-14 | 2018-09-14 | Method for processing business, network system and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109194760A (en) |
Cited By (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109831504A (en) * | 2019-01-31 | 2019-05-31 | 泰康保险集团股份有限公司 | Micro services request processing method, device and equipment |
| CN109922158A (en) * | 2019-03-22 | 2019-06-21 | 泰康保险集团股份有限公司 | Data processing method, device, medium and electronic equipment based on micro services |
| CN109981757A (en) * | 2019-03-13 | 2019-07-05 | 青岛特锐德电气股份有限公司 | A kind of API gateway load-balancing algorithm towards small-scale micro services framework |
| CN110149364A (en) * | 2019-04-15 | 2019-08-20 | 厦门市美亚柏科信息股份有限公司 | Method, apparatus, the storage medium of micro services are provided based on data service platform |
| CN110365700A (en) * | 2019-07-30 | 2019-10-22 | 上海派拉软件股份有限公司 | A kind of access control method based on service |
| CN110381112A (en) * | 2019-06-05 | 2019-10-25 | 黄疆 | A kind of storage device cluster based on micro services framework |
| CN110727557A (en) * | 2019-09-23 | 2020-01-24 | 北京百度网讯科技有限公司 | Log collector management and control method, platform, electronic device and storage medium |
| CN110825539A (en) * | 2019-11-07 | 2020-02-21 | 中国联合网络通信集团有限公司 | Business processing method and device |
| CN111092774A (en) * | 2019-12-25 | 2020-05-01 | 中国联合网络通信集团有限公司 | Configuration method and equipment of acquisition gateway |
| CN111580846A (en) * | 2020-05-15 | 2020-08-25 | 厦门靠谱云股份有限公司 | Micro-service gray scale publishing method based on mixed framework |
| CN111885114A (en) * | 2020-06-29 | 2020-11-03 | 百度在线网络技术（北京）有限公司 | Method, device and storage medium for upgrading application program interface module in gateway |
| CN112104688A (en) * | 2020-05-19 | 2020-12-18 | 福建电力职业技术学院 | Integrated service type mobile operation terminal application management system |
| CN112217840A (en) * | 2020-12-09 | 2021-01-12 | 杭州筋斗腾云科技有限公司 | Distributed network resource safety access management system and user port |
| CN112231168A (en) * | 2020-09-03 | 2021-01-15 | 平安信托有限责任公司 | Micro server control method, device, equipment and storage medium |
| CN112286650A (en) * | 2020-11-04 | 2021-01-29 | 中国电力财务有限公司 | Method and device for issuing distributed service |
| CN112367299A (en) * | 2020-10-16 | 2021-02-12 | 深圳市科漫达智能管理科技有限公司 | Application program interface API management method and related device |
| CN112448978A (en) * | 2019-08-30 | 2021-03-05 | 中国移动通信集团河北有限公司 | Data management method and system |
| CN112468580A (en) * | 2020-11-25 | 2021-03-09 | 政采云有限公司 | Method, device, equipment and storage medium for calling business service |
| CN112463118A (en) * | 2020-11-26 | 2021-03-09 | 北京宏景世纪软件股份有限公司 | Control method, device, terminal and system of software development framework |
| CN112465432A (en) * | 2020-12-07 | 2021-03-09 | 合肥维天运通信息科技股份有限公司 | Waybill information processing method |
| WO2021052026A1 (en) * | 2019-09-17 | 2021-03-25 | 中兴通讯股份有限公司 | Micro-service upgrading method, electronic device and readable storage medium |
| CN112769687A (en) * | 2020-12-10 | 2021-05-07 | 前海飞算科技(深圳)有限公司 | API gateway platform |
| CN112953771A (en) * | 2021-02-22 | 2021-06-11 | 安徽兆尹信息科技股份有限公司 | Financial asset management system based on micro-service and decoupling method |
| CN113220377A (en) * | 2021-05-11 | 2021-08-06 | 上海销氪信息科技有限公司 | Method, system and storage medium for managing and controlling functions of micro-service |
| CN113382051A (en) * | 2021-06-01 | 2021-09-10 | 中国民航信息网络股份有限公司 | Full-link gray scale publishing method and gray scale publishing system |
| CN113744853A (en) * | 2021-01-18 | 2021-12-03 | 北京京东拓先科技有限公司 | Service processing method, system, device, equipment and storage medium |
| CN113946328A (en) * | 2021-10-18 | 2022-01-18 | 泰康保险集团股份有限公司 | Service processing method and system, storage medium and electronic equipment |
| CN115883405A (en) * | 2022-11-25 | 2023-03-31 | 上海浦东发展银行股份有限公司 | Service detection system |
| WO2025083717A1 (en) * | 2023-10-17 | 2025-04-24 | Jio Platforms Limited | Method and system for managing communication between external systems and mano frameworks |
-
2018
- 2018-09-14 CN CN201811083701.0A patent/CN109194760A/en not_active Withdrawn
Cited By (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109831504B (en) * | 2019-01-31 | 2022-01-25 | 泰康保险集团股份有限公司 | Micro service request processing method, device and equipment |
| CN109831504A (en) * | 2019-01-31 | 2019-05-31 | 泰康保险集团股份有限公司 | Micro services request processing method, device and equipment |
| CN109981757A (en) * | 2019-03-13 | 2019-07-05 | 青岛特锐德电气股份有限公司 | A kind of API gateway load-balancing algorithm towards small-scale micro services framework |
| CN109981757B (en) * | 2019-03-13 | 2022-07-08 | 青岛特来电新能源科技有限公司 | API gateway load balancing method for small-scale micro-service architecture |
| CN109922158A (en) * | 2019-03-22 | 2019-06-21 | 泰康保险集团股份有限公司 | Data processing method, device, medium and electronic equipment based on micro services |
| CN110149364A (en) * | 2019-04-15 | 2019-08-20 | 厦门市美亚柏科信息股份有限公司 | Method, apparatus, the storage medium of micro services are provided based on data service platform |
| CN110381112A (en) * | 2019-06-05 | 2019-10-25 | 黄疆 | A kind of storage device cluster based on micro services framework |
| CN110365700A (en) * | 2019-07-30 | 2019-10-22 | 上海派拉软件股份有限公司 | A kind of access control method based on service |
| CN112448978A (en) * | 2019-08-30 | 2021-03-05 | 中国移动通信集团河北有限公司 | Data management method and system |
| WO2021052026A1 (en) * | 2019-09-17 | 2021-03-25 | 中兴通讯股份有限公司 | Micro-service upgrading method, electronic device and readable storage medium |
| CN110727557A (en) * | 2019-09-23 | 2020-01-24 | 北京百度网讯科技有限公司 | Log collector management and control method, platform, electronic device and storage medium |
| CN110825539A (en) * | 2019-11-07 | 2020-02-21 | 中国联合网络通信集团有限公司 | Business processing method and device |
| CN111092774A (en) * | 2019-12-25 | 2020-05-01 | 中国联合网络通信集团有限公司 | Configuration method and equipment of acquisition gateway |
| CN111580846A (en) * | 2020-05-15 | 2020-08-25 | 厦门靠谱云股份有限公司 | Micro-service gray scale publishing method based on mixed framework |
| CN112104688A (en) * | 2020-05-19 | 2020-12-18 | 福建电力职业技术学院 | Integrated service type mobile operation terminal application management system |
| CN111885114A (en) * | 2020-06-29 | 2020-11-03 | 百度在线网络技术（北京）有限公司 | Method, device and storage medium for upgrading application program interface module in gateway |
| CN111885114B (en) * | 2020-06-29 | 2023-03-24 | 百度在线网络技术（北京）有限公司 | Method, device and storage medium for upgrading application program interface module in gateway |
| CN112231168A (en) * | 2020-09-03 | 2021-01-15 | 平安信托有限责任公司 | Micro server control method, device, equipment and storage medium |
| CN112367299A (en) * | 2020-10-16 | 2021-02-12 | 深圳市科漫达智能管理科技有限公司 | Application program interface API management method and related device |
| CN112367299B (en) * | 2020-10-16 | 2023-04-18 | 深圳市科漫达智能管理科技有限公司 | Application program interface API management method and related device |
| CN112286650A (en) * | 2020-11-04 | 2021-01-29 | 中国电力财务有限公司 | Method and device for issuing distributed service |
| CN112468580A (en) * | 2020-11-25 | 2021-03-09 | 政采云有限公司 | Method, device, equipment and storage medium for calling business service |
| CN112463118A (en) * | 2020-11-26 | 2021-03-09 | 北京宏景世纪软件股份有限公司 | Control method, device, terminal and system of software development framework |
| CN112465432A (en) * | 2020-12-07 | 2021-03-09 | 合肥维天运通信息科技股份有限公司 | Waybill information processing method |
| CN112217840B (en) * | 2020-12-09 | 2021-04-13 | 杭州筋斗腾云科技有限公司 | Distributed network resource safety access management system and user port |
| US11457046B2 (en) | 2020-12-09 | 2022-09-27 | Hangzhou Jindoutengyun Technologies Co., Ltd. | Distributed network resource security access management system and user portal |
| CN112217840A (en) * | 2020-12-09 | 2021-01-12 | 杭州筋斗腾云科技有限公司 | Distributed network resource safety access management system and user port |
| CN112769687A (en) * | 2020-12-10 | 2021-05-07 | 前海飞算科技(深圳)有限公司 | API gateway platform |
| CN113744853A (en) * | 2021-01-18 | 2021-12-03 | 北京京东拓先科技有限公司 | Service processing method, system, device, equipment and storage medium |
| CN112953771A (en) * | 2021-02-22 | 2021-06-11 | 安徽兆尹信息科技股份有限公司 | Financial asset management system based on micro-service and decoupling method |
| CN113220377A (en) * | 2021-05-11 | 2021-08-06 | 上海销氪信息科技有限公司 | Method, system and storage medium for managing and controlling functions of micro-service |
| CN113382051A (en) * | 2021-06-01 | 2021-09-10 | 中国民航信息网络股份有限公司 | Full-link gray scale publishing method and gray scale publishing system |
| WO2022252856A1 (en) * | 2021-06-01 | 2022-12-08 | 中国民航信息网络股份有限公司 | Full-link grayscale releasing method and grayscale releasing system |
| CN113946328A (en) * | 2021-10-18 | 2022-01-18 | 泰康保险集团股份有限公司 | Service processing method and system, storage medium and electronic equipment |
| CN115883405A (en) * | 2022-11-25 | 2023-03-31 | 上海浦东发展银行股份有限公司 | Service detection system |
| WO2025083717A1 (en) * | 2023-10-17 | 2025-04-24 | Jio Platforms Limited | Method and system for managing communication between external systems and mano frameworks |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109194760A (en) | Method for processing business, network system and server | |
| US10719369B1 (en) | Network interfaces for containers running on a virtual machine instance in a distributed computing environment | |
| CN109104483B (en) | Micro-service dynamic load balancing method and device based on event notification | |
| CN101194233B (en) | System and method of testing wireless component applications | |
| US8117297B2 (en) | System and method of device-to-server registration | |
| CN112788031B (en) | Micro-service interface authentication system, method and device based on Envoy architecture | |
| CN110532025B (en) | Data processing method, device and equipment based on micro-service architecture and storage medium | |
| CN111176794B (en) | Container management method, device and readable storage medium | |
| EP1991941A1 (en) | Apparatus and methods for managing time sensitive application privileges on a wireless device | |
| CN110268731B (en) | Techniques for obtaining a network access profile | |
| CN110268730B (en) | Techniques for managing subscriptions with operators | |
| CN112968963A (en) | WebSocket-based method for user forced real-time offline | |
| CN110661780A (en) | Wireless city data sharing method and system based on SAAS application | |
| US20180268126A1 (en) | Dynamically controlling access to devices | |
| CN117319930A (en) | Communication service switching and request sending method, device, equipment and storage medium | |
| US20230214207A1 (en) | Device upgrade control method and apparatus, and computer device and storage medium | |
| CN112671945A (en) | Method, device, computer equipment and storage medium for managing IP proxy pool | |
| CN1939035B (en) | Method and apparatus for communicating data between computer devices | |
| CN115941795B (en) | Data transmission method, device, electronic device and storage medium | |
| CN110784551A (en) | Data processing method, device, equipment and medium based on multiple tenants | |
| CN115412294A (en) | Platform service-based access method and device, storage medium, and electronic device | |
| CN117014226B (en) | Service request authentication method, device, equipment, system and storage medium | |
| CN101969449B (en) | Automatic filling system for mobile communication equipment terminal browser and application method thereof | |
| CN114356456B (en) | Business processing method, device, storage medium and electronic device | |
| CN111176782B (en) | Online experiment method and device |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20190111 |
|
| WW01 | Invention patent application withdrawn after publication |