CN112350978A - Service processing method, system, device and storage medium - Google Patents
Service processing method, system, device and storage medium Download PDFInfo
- Publication number
- CN112350978A CN112350978A CN201910731249.2A CN201910731249A CN112350978A CN 112350978 A CN112350978 A CN 112350978A CN 201910731249 A CN201910731249 A CN 201910731249A CN 112350978 A CN112350978 A CN 112350978A
- Authority
- CN
- China
- Prior art keywords
- service
- micro
- microservice
- request
- account
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 26
- 238000012545 processing Methods 0.000 claims abstract description 119
- 238000000034 method Methods 0.000 claims abstract description 58
- 230000015654 memory Effects 0.000 claims description 29
- 230000008569 process Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 13
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000004806 packaging method and process Methods 0.000 claims description 2
- 238000011161 development Methods 0.000 description 49
- 230000006870 function Effects 0.000 description 40
- 238000007726 management method Methods 0.000 description 30
- 238000010586 diagram Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 7
- 230000001360 synchronised effect Effects 0.000 description 7
- 230000004044 response Effects 0.000 description 6
- 230000015556 catabolic process Effects 0.000 description 5
- 238000010276 construction Methods 0.000 description 5
- 238000006731 degradation reaction Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 238000010168 coupling process Methods 0.000 description 4
- 238000005859 coupling reaction Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 230000008520 organization Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- 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
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- 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
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
- H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application discloses a service processing method, a service processing device, equipment and a storage medium, which are applied to a service processing system, wherein the method comprises the following steps: receiving a login request at an interface gateway micro-service, and sending an account and a password carried by the login request to an authentication micro-service; after authentication is passed based on the account and the password, the authentication microservice distributes a token for the account; receiving a service request corresponding to the account at the interface gateway micro-service, acquiring a token carried by the service request and a token distributed for the account, determining that the token carried by the service request is the same as the token distributed for the account, and sending the service request to the service micro-service; processing the service request at the service microservice; therefore, the safety of the service processing system formed by the micro-service is improved.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, and relates to but is not limited to a service processing method, a system, equipment and a storage medium.
Background
In the related art, in the software design of the single application development architecture, the software framework includes a 3-layer model shown in fig. 1: a presentation layer 101, a business logic layer 102, and a data access layer 103. For example, in a movie ticketing system, presentation layer 101: for direct interaction with a user, also called interaction layer, generally comprises: user Interfaces (UIs), hypertext Markup Language (HTML) pages, and the like. The business logic layer 102: namely, the service logic processing layer, the information input by the user can be displayed to the user after being processed by the service logic layer, and the information can include a movie module, a user module and the like. A data access layer: the method is used for operating the database, a user can generate a large amount of data on the presentation layer through the service logic layer and store the data in the database of the data access layer, and the data access layer is used for performing read-write interactive operation on the database.
Although the classical 3-layer model described above is divided in the software design, all the business modules of different business scenarios are coupled together. A typical development framework of a single-architecture application is to put all the presentation layers, service logic layers, and data access layers of a service scenario into one project, and finally compile, package, and deploy the project on one server or multiple machines. For example, the typical J2EE project, which packages JSP representing layers, HTML, Controller of business logic layer, Service and Dao of data access layer into war packet, and deploys it in Tomcat, Jetty or other Servlet container to run. Therefore, the service modules in different application scenarios have high coupling.
In order to reduce the coupling of business modules in different scenes, the whole application program is divided into a plurality of micro services, and different business services are provided through different micro services.
Disclosure of Invention
The embodiment of the application provides a service processing method, a system, equipment and a storage medium.
The technical scheme of the embodiment of the application is realized as follows:
the embodiment of the application provides a service processing method, which is applied to a service processing system, wherein the service processing system is composed of micro services, the micro services comprise an interface gateway micro service, an authentication micro service and a service micro service, and the method comprises the following steps:
receiving a login request at an interface gateway micro-service, and sending an account and a password carried by the login request to an authentication micro-service;
after authentication is passed based on the account and the password, the authentication microservice distributes a token for the account;
receiving a service request corresponding to the account at the interface gateway micro-service, acquiring a token carried by the service request and a token distributed for the account, determining that the token carried by the service request is the same as the token distributed for the account, and sending the service request to the service micro-service;
and processing the service request at the service microservice.
The embodiment of the application also provides a service processing system, wherein the service processing system is composed of micro services, and the micro services comprise interface gateway micro services, authentication micro services and service micro services; wherein,
the interface gateway micro-service is used for receiving a login request and sending an account and a password carried by the login request to the authentication micro-service;
the authentication microservice is used for distributing tokens to the account after the account and the password are authenticated;
the interface gateway micro-service is further configured to receive a service request corresponding to the account, acquire a token carried by the service request and a token allocated to the account, determine that the token carried by the service request is the same as the token allocated to the account, and send the service request to the service micro-service;
and the service microservice processes the service request.
The embodiment of the application also provides a business processing device, which comprises a processor and a memory for storing a computer program capable of running on the processor; the processor is configured to execute the steps in the service processing method when the computer program is run.
The embodiment of the application also provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the service processing method is realized.
The service processing method, system, device and storage medium provided by the embodiment of the application, after determining that the login request passes the authentication, allocate a token to the account, and when receiving the service request corresponding to the account, determine whether the token carried by the service request is the same as the token allocated to the line number, and when determining that the token carried by the service request is the same, consider that the service request is a legal service request, and process the service request, so that the service request processed by the micro service is the micro service authorized by the authentication micro service, thereby improving the security of the service processing system formed by the micro service.
Drawings
FIG. 1 is a diagram of a software framework for monolithic application development in the related art;
fig. 2 is an alternative schematic structural diagram of a service processing system according to an embodiment of the present application;
fig. 3 is an alternative flow chart of a service processing method according to an embodiment of the present application;
fig. 4 is an alternative schematic structural diagram of a service processing system according to an embodiment of the present application;
fig. 5 is an alternative schematic structural diagram of a service processing system according to an embodiment of the present application;
fig. 6 is an alternative flow chart of the service processing method according to the embodiment of the present application;
fig. 7 is an alternative schematic structural diagram of a service processing system according to an embodiment of the present application;
fig. 8 is a schematic diagram of an alternative functional structure of a service processing system according to an embodiment of the present application;
fig. 9 is a schematic diagram of an alternative technical architecture of a service processing system according to an embodiment of the present application;
fig. 10 is an alternative interaction flow diagram of a service processing method according to an embodiment of the present application;
fig. 11 is an alternative development mutual flow diagram of the service processing method according to the embodiment of the present application;
fig. 12 is a schematic diagram of an alternative configuration process of the service processing system according to the embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and specific embodiments.
The service processing method provided in the embodiment of the present application is applied to a service processing system, where the service processing system is composed of micro services, and as an example, a structure of a service processing system 200 may be as shown in fig. 2, and includes: interface gateway microservice 201, authentication microservice 202, and business microservice 203 (business microservice 203-1 and business microservice 203-2 are shown as examples).
The interface gateway microservice 201 receives the login request R1, and sends the account A and the password a carried by the login request R1 to the authentication microservice 202. After the authentication microservice 202 determines that the account a and the password a pass authentication, a token T is allocated to the account a. The interface gateway microservice 201 receives a service request R2 corresponding to an account A, acquires a token T 'carried by the service request and a token T allocated to the account A, determines that the token T' carried by the service request R2 is the same as the token T allocated to the account, and sends the service request R2 to the service microservice 203; at the service microservice 203, the service request R2 is processed.
In practical applications, when the interface gateway microservice 201 allocates the service request R2 to the service microservice 203-1, the service microservice 203-1 processes the service request R2. When the interface gateway microservice 201 allocates the service request R2 to the service microservice 203-2, the service microservice 203-2 processes the service request R2.
The service processing method in the embodiment of the present application is described based on the service processing system shown in fig. 2, and as shown in fig. 3, the method includes the following steps:
step 301: and receiving a login request at an interface gateway micro-service, and sending an account and a password carried by the login request to an authentication micro-service.
When a user logs in the service processing system for the first time based on the terminal, an account and a password are input based on a login interface provided by the login service processing system, a login request is triggered based on the login interface displayed on the login interface, and the login request is sent to the user. Here, the login request may carry an account and a password input by the user.
The method comprises the steps of receiving a login request sent by a client in an interface gateway micro-service of a business processing system, analyzing the received login request to obtain an account and a password carried by the login request, and sending the account and the password to an authentication micro-service of the business processing system.
The interface gateway microservice may forward the login request directly to the authentication microservice, or may forward only the account and password to the authentication microservice.
Step 302: and after the authentication microservice determines that the account and the password pass authentication, distributing a token for the account.
And after the authentication micro-service receives the account and the password sent by the interface gateway micro-service, acquiring a storage password corresponding to the account based on the account, and matching the received password with the acquired storage password. If the password is matched with the stored password, the login request is confirmed to pass the authentication; and if the password does not match the stored password, determining that the login request authentication fails. Wherein, when the password is the same as the stored password, it can be determined that the password matches the stored password. Here, the stored password is a password corresponding to the account stored in the system, and may be a password set by the user at the time of password setting.
In practical application, when the authentication micro-service does not acquire the storage password corresponding to the account, it is determined that the account and the password are not verified, and when the storage password corresponding to the account is acquired, the password and the storage password are matched.
And after the account and the password are determined to pass the authentication, distributing a token for the account. Here, in the service processing system, a token pool may be set, where the token pool includes a plurality of tokens, and each token is set with a corresponding allocation identifier to indicate whether the token has been allocated. When a token is assigned to an account, the assignment flag is in an assigned state; if the token is not assigned to the account, the assignment flag is in an unassigned state. The authentication microserver obtains any non-token with the allocation identifier in a non-allocation state from the token pool and allocates the non-token to the account. It should be noted that, when the authentication microservice allocates tokens to the account, the tokens allocated to different accounts are different, for example: the token assigned to account a is T1, the token assigned to account B is T2, and the tokens assigned to the same account in different assignment processes are different, such as: the first time the account A was assigned a token of T1 and the second time the account was assigned a token of T3.
In this embodiment of the application, the authentication microservice may further use an account as a parameter, and calculate a token allocated to each account based on a set algorithm. The embodiment of the present application does not limit the specific allocation manner for allocating tokens to the account.
In practical application, the authentication microservice can allocate a token with a corresponding level to the account according to the level of the account. The service processing system sets different access rights for the service requests corresponding to the accounts with different levels. Such as: the grades of the accounts comprise a first grade, a second grade and a third grade, wherein the service request corresponding to the account with the grade of the first grade can access 20% of resources of the service processing system, the service request corresponding to the account with the grade of the second grade can access 60% of resources of the service processing system, and the service request corresponding to the account with the grade of the third grade can access 200% of resources of the service processing system. In the embodiment of the application, the difference of the accounts with different grades can be set according to actual requirements.
And after the authentication micro-service allocates the token for the account, sending the allocated token to the interface gateway micro-service.
Step 303: and receiving a service request corresponding to the account at the interface gateway micro-service, acquiring a token carried by the service request and a token distributed for the account, determining that the token carried by the service request is the same as the token distributed for the account, and sending the service request to the service micro-service.
And after receiving the token distributed by the account carried by the authentication micro-service for the login request, the receiving gateway micro-service sends a login response responding to the login request to the client, and the distributed token is carried in the login response indicating successful authentication.
And when the client receives the login response, the login of the service processing system is completed. When the client sends a service request to the service processing system without pushing out the current login, the client can carry a token returned by the service processing system in the service request.
When the interface gateway micro-service received by the service processing system receives the service request sent by the client, the received service request is analyzed, and whether the service request carries a token or not is determined. And when the service request does not carry the token, determining that the received service request is an illegal service request. When the service request carries the token, the token distributed for the account is obtained according to the account in the service request, and the token carried by the service request is matched with the token distributed for the account. And if the token carried by the service request is the same as the token distributed to the account, determining that the service request is a legal service request, and when the token carried by the service request is different from the token distributed to the account, determining that the service request is an illegal service request.
And when the interface gateway micro-service determines that the service request is a legal service request, sending the service request to the service micro-service. When the interface gateway micro-service determines that the service request is an illegal service request, the service request is not processed or is directly discarded. When the interface gateway micro-service determines that the service request is an illegal service request, an illegal prompt can be returned to the client to prompt the user that the current service request is an illegal service request.
Step 304: and processing the service request at the service microservice.
And after the service request receives the service request sent by the interface gateway microservice, processing the service request. Here, a plurality of business microservices of different business types may be included in the business processing system, such as: user management microservices, organization management microservices, role management microservices, metadata management microservices and the like. And processing the service micro-service of the corresponding service type according to different service types.
In one embodiment, the interface gateway microservice performing the sending of the service request to the service microservice includes: determining the service type of the received service request, and determining a target service microservice corresponding to the service type in the service microservices; correspondingly, the service request is processed in the target service microservice.
Before the interface gateway micro-service sends the service request to the service module, the type of the service request is determined, and the target service micro-service for processing the service request is determined according to the service type of the service request. Such as: and when the service request is a service request of a role management class, determining the role management micro-service as a target micro-service. For another example: and when the service request is a service request of an organization management class, determining the organization management micro-service as a target micro-service.
And after determining the target micro service, the interface gateway micro service forwards the service request to the target service micro service, so that the target service micro service processes the service request.
In the embodiment of the application, after the login request is determined to pass authentication, a token is allocated to the account, when a service request corresponding to the account is received, whether the token carried by the service request is the same as the token allocated to the line number is judged, if the token carried by the service request is determined to be the same as the token allocated to the line number, the service request is considered to be a legal service request, and the service request is processed, otherwise, the service request is not processed, so that different service micro-services only need to authenticate one-time authorization of the micro-services, and the safety of a service processing system formed by the micro-services is improved.
In an embodiment, as an example, a service system provided in an embodiment of the present application may be as shown in fig. 4, and includes: interface gateway microservice 201, authentication microservice 202, business microservice 203 (shown illustratively as business microservice 203-1 and business microservice 203-2), and service registration microservice 204. In the service registration microservice 204, microservices in the service processing system are registered, and an association relationship between different microservices is constructed.
When the business processing system is started, each micro service is enabled to send a message to the service registration micro service, and each micro service is registered with the externally provided business service to form a registration list. And associating different micro services through the service provided by each micro service in the registration list. The service registration micro-service is used for maintaining a registration list, wherein the registration list is a mapping table of a service interface name and a micro-service address, and stores service information provided by all micro-services in the service system.
When a new micro service is added in the business processing system, the added new micro service is enabled to send a message to the service registration micro service, and the business service provided by the added micro service to the outside is added into the registration list so as to register the new micro service.
When the micro service to be deleted exists in the service processing system, the micro service to be deleted is enabled to send a message to the service registration micro service, and the service provided by the micro service to be deleted is deleted from the registration list so as to update the registration list.
In practical application, the service processing system further includes a service discovery micro-service to discover a new micro-service added in the service processing system and a micro-service to be deleted, and to discover an update of the service processing system.
Here, the micro service registered in the service registration micro service is synchronized with the micro service included in the business system. And the dynamic registration of the micro-service in the service processing system is realized through the service registration micro-service.
In one embodiment, the microservice includes a first microservice and a second microservice, the first microservice and the second microservice being different microservices in the business processing system; the method further comprises the following steps:
after the first micro service processes the service request, sending a calling message to the service registration micro service; registering micro service in the service, determining address information of the second micro service according to the first micro service, and returning the address information of the second micro service to the first micro service; and calling the second micro service based on the address information of the second micro service in the first micro service, and sending the processed service request to the called second micro service.
The first microservice and the second microservice are each different microservices registered in a service registration microservice. Such as: the first micro service is an interface gateway micro service, and the second micro service is an authentication micro service. For another example: the first micro service is an authentication micro service, and the second micro service is an interface gateway micro service. For another example: the first microservice is the business microservice 203-1 shown in fig. 3, and the second microservice is the business microservice 203-2 shown in fig. 3. Still alternatively, the first microservice is the business microservice 203-2 shown in fig. 3, and the second microservice is the business microservice 203-1 shown in fig. 3.
After the first micro service processes the service request, the requested service request needs to be sent to the next micro service for processing, and the first micro service sends a call message to the service registration micro service to request the address information of the next micro service. The first microservice and other microservices in the business processing system are independent from each other, the first microservice cannot determine which microservice is in the business processing system, and when data transmission does not exist between the first microservice and other microservices in the business processing system, connection is not established between the first microservice and other microservices.
After the micro service is registered in the service and the call message of the first micro service is received, the next required service is determined according to the service required by the current service request and the service provided by the first micro service, and the second micro service capable of improving the service is determined according to the next required service.
And after the service registration micro-service determines the second micro-service, the address information of the second micro-service is acquired in the service registration list, and the acquired address information of the second micro-service is returned to the first micro-service so as to respond to the calling message of the first micro-service. Here, the address information may include a service interface name and a micro service address, and the micro service address may be an Internet Protocol (Internet Protocol) IP address.
In practical applications, one IP address may correspond to one or more micro services, and service interface names of different micro services are different, so that one micro service can be uniquely identified by the micro service address and the service interface name.
And calling the second micro service based on the address information of the second micro service in the first micro service, and sending the processed service request to the called second micro service.
In an embodiment, in the first microservice, based on the address information of the second microservice, invoking the second microservice, and sending the processed service request to the invoked second microservice to invoke the second microservice, the following steps may be performed:
based on the address information, the message drives an interface between the first micro service and the second micro service, the second micro service is called based on the driven interface, and the processed service request is sent to the called second micro service based on the driven interface.
When the first micro service receives the address information of the second micro service from the service registration micro service, the first micro service sends a message to the second micro service by taking the received address information as a target address so as to drive an interface between the first micro service and the second micro service, and connection is established between the first micro service and the second micro service based on the driven interface. The communication protocol supported by the driven interface may be independent of the first microservice and the second microservice. For example: the interface between the service registration microservice and the interface gateway microservice may support the hypertext Transfer Protocol (HTTP) Protocol, and may also support the JS Object Notation (JavaScript Object Notation) Protocol.
After the connection is established between the first micro service and the interface based on the drive of the second micro service, the first micro service sends the processed service processing request information to the second micro service through the drive interface.
In the embodiment of the application, the micro-services in the service processing system are dynamically registered through the service registration micro-service, and the independent micro-services are called through the service registration micro-service.
In an embodiment, as an example, a service system provided in an embodiment of the present application may be as shown in fig. 5, and includes: interface gateway microservice 201, authentication microservice 202, business microservice 203 (business microservice 203-1 and business microservice 203-2 are shown as examples), and front end microservice 205. In the front-end microserver 205, the service request is triggered based on the operation request of the user, and the processing result of the target service microserver to the service request is output. Here, the front-end microservice can be used as a client of the business processing system to realize the interaction between the business processing system and the user.
The front-end micro-service and other micro-services in the business processing system may be located on the same functional entity, such as: the front-end micro-service and other micro-services in the service processing system are simultaneously positioned on the terminal.
The front-end micro-service and other micro-services in the service processing system may also be located on different functional entities, respectively, such as: the front-end micro-service is positioned on the terminal, and other micro-services in the service processing system are positioned on a server connected with the terminal through a network.
In an embodiment, the service processing method provided in the embodiment of the present application further includes:
receiving, at the front-end microservice, a token assigned to the account; the token distributed for the account is packaged in the service request, and the service request packaged with the token distributed for the account is sent to the interface gateway microservice;
and receiving a processing result of the business request by the business micro service at the interface gateway micro service, and sending the processing result to the front-end micro service.
As an example, the service processing method provided in the embodiment of the present application may be as shown in fig. 6, and includes:
step 601: and receiving a login request at an interface gateway micro-service, and sending an account and a password carried by the login request to an authentication micro-service.
Step 602: and after the authentication microservice determines that the account and the password pass authentication, distributing a token for the account.
Step 603: and receiving the token distributed to the account by the front-end micro service.
Step 604: and receiving the service request at the front-end micro service, packaging the token distributed for the account in the service request, and sending the service request packaged with the token distributed for the account to the interface gateway micro service.
Step 605: receiving a service request corresponding to the account at an interface gateway micro-service, acquiring a token carried by the service request and a token distributed for the account, determining that the token carried by the service request is the same as the token distributed for the account, and sending the service request to the service micro-service;
step 606: processing the service request in service microservice;
step 607: and receiving a processing result of the business request by the business micro service at an interface gateway micro service, and sending the processing result to the front-end micro service.
Step 608: and outputting the processing result of the target business microservice to the business request at the front-end microservice.
As an example, a service system provided in this embodiment of the present application may be as shown in fig. 7, and includes: interface gateway microservice 201, authentication microservice 202, traffic microservice 203 (illustratively shown as traffic microservice 203-1 and traffic microservice 203-2), and service flow control microservice 206. In the service flow control microservice 206, the running microservices are monitored, and resources are correspondingly allocated according to the priority of each running microservice.
And the service flow control micro-service monitors the micro-service operated in the service processing system, acquires the priority of the micro-service operated, and allocates resources for each priority according to the priority of each micro-service operated. Here, the allocated resource may be traffic of an interface gateway microservice. When the resources are allocated to the running micro-services, the resources are allocated to the running micro-services according to the specific resource amount, and the resources which can be used by the micro-services can also be controlled according to the proportion of the total resources occupied by the resources allocated to the running micro-services.
And when the resources are distributed for each priority according to the priority of each micro-service, determining the corresponding weight according to the priority of each running micro-service, and distributing the resources based on the weight of each micro-service. Such as: the method comprises the steps that a micro service A and a micro service B run in a service processing system, and the priority of the micro service A is higher than that of the micro service B, the weight corresponding to the micro service A is set to be 4, the weight corresponding to the micro service B is set to be 1, at the moment, 80% of flow of the micro service of an interface gateway is distributed to the micro service A, and 20% of flow of the micro service of the interface gateway is distributed to the micro service B;
when the resources are distributed for each priority according to the priority of each micro-service, a limiting threshold can be dynamically set for the micro-service with high priority, and the resources occupied by the micro-service with high priority are limited within the limiting threshold, so that all traffic cannot be occupied by the micro-service with high priority, and the micro-service with low priority cannot be used without resources.
In one embodiment, the method includes the steps of controlling a micro service at the service flow, detecting the total resource usage amount used by the running micro service, and adjusting the priority of the running micro service when the total resource usage amount is larger than a set resource usage threshold.
When the service flow control micro-service allocates resources for each running micro-service, the priority of each running micro-service can be adjusted according to the current resource use condition, so that the resources which can be used by each running micro-service can be updated.
Here, the service monitoring microservice may periodically obtain a total resource usage amount used by the running microservice, compare the obtained total resource usage amount with a set resource usage threshold, and when the total resource usage amount is greater than the resource usage threshold, indicate that the microservice is currently in a service request concurrence peak period, adjust a priority of the running microservice, for example: and the priority of the micro service with high priority is adjusted to be high, or the priority of the micro service with low priority is adjusted to be low.
Here, the setting of the priority of the microservice having a low priority is referred to as service degradation processing, and the service degradation processing can perform the priority degradation processing on the microservice having a low priority, that is, not very important, and give up system resources to the microservice having a high priority as much as possible.
In the embodiment of the application, the total resources in the business processing system are limited, and the business request is unlimited. And if the service request is in a concurrency peak, the usability of the core function micro-service of the service processing system is ensured through service degradation processing, so that the service performance of the core function micro-service is prevented from being influenced by the concurrency of the service request, the possibility of unavailability of the core function micro-service is reduced, and the overall service performance of the service processing system is improved.
The embodiment of the present application further provides a service processing system 200 composed of micro services, which is exemplarily shown in fig. 2 and includes:
the interface gateway microservice 201 is used for receiving a login request and sending an account and a password carried by the login request to the authentication microservice 202;
the authentication microservice 202 is used for distributing tokens to the account after the account and the password are authenticated;
the interface gateway microservice 201 is further configured to receive a service request corresponding to the account, obtain a token carried by the service request and a token allocated to the account, determine that the token carried by the service request is the same as the token allocated to the account, and send the service request to the service microservice 203;
and the service microservice 203 processes the service request.
In one embodiment, the interface gateway microservice is further configured to:
determining the service type of the received service request, and determining a target service microservice corresponding to the service type in the service microservices;
correspondingly, the service request is processed in the target service microservice.
In one embodiment, the business processing system 200 further comprises: a service registration microservice to:
and registering the micro-services and constructing an association relation between different micro-services.
In one embodiment, the microservice includes a first microservice and a second microservice,
the first micro service is used for sending a calling message to the service registration micro service after processing the service request;
the service registration micro-service is used for determining the address information of the second micro-service according to the first micro-service and returning the address information of the second micro-service to the first micro-service;
the first micro service is used for calling the second micro service based on the address information of the second micro service and sending the processed service request to the called second micro service.
In one embodiment, the first microservice is further configured to: based on the address information, the message drives an interface between the first micro service and the second micro service, the second micro service is called based on the driven interface, and the processed service request is sent to the called second micro service based on the driven interface.
In one embodiment, the microservice of the business processing system 200 further comprises: the micro-service of the front end,
and the front-end micro service is used for receiving the service request and outputting a processing result of the target service micro service on the service request.
In an embodiment, the front-end microservice is configured to receive a token allocated to the account, encapsulate the token allocated to the account in the service request, and send the service request encapsulated with the token allocated to the account to the interface gateway microservice;
and the interface gateway micro-service is used for receiving a processing result of the business micro-service on the business request and sending the processing result to the front-end micro-service.
In one embodiment, the microservice of the business processing system 200 further comprises: the service flow control micro-service controls the flow,
and the service flow control micro-service is used for monitoring the running micro-service and correspondingly allocating resources according to the priority of each running micro-service.
In an embodiment, the service flow control microservice is further configured to:
detecting the total resource usage amount used by the running micro-service, and adjusting the priority of the running micro-service when the total resource usage amount is larger than the set resource usage threshold value.
It should be noted that, the service processing system provided in the foregoing embodiment is only illustrated by dividing the program modules, and in practical applications, the processing allocation may be completed by different program modules according to needs, that is, the internal structure of the system is divided into different program modules to complete all or part of the processing described above. In addition, the service processing system and the service processing method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.
The service processing method provided in the embodiment of the present application is further described in a specific application scenario below.
Here, the technical deficiency of the software framework shown in fig. 1 will be described first.
The software framework shown in fig. 1 has several technical drawbacks:
1. high code repetition rate
In actual project division, development users are respectively responsible for several functions in an application program, even though modules with overlapped functions exist among the development users, the overlapped functions are often realized according to the design of the development users, and the development users do not share class libraries, so that the design of different development users is different for the part with overlapped functions. Here, the reasons why different development users implement overlapping functions according to their own designs include:
from a technical architecture perspective: the traditional vertical architecture is characterized in that a local Application Programming Interface (API) is called, service splitting and mutual calling do not exist, and what functions are used is developed locally, so that the traditional vertical architecture is very convenient and does not excessively depend on other functional modules.
From the assessment perspective: sharing is difficult to enforce. Developers only need to be responsible for the delivery quality of the modules developed by the developers, and have no obligation to provide and maintain the public class library for others.
From the time control point of view: time dependence control is difficult, and for users of public class libraries, the function is provided by a function provider different from the user, but the function provider may have more important things to do, and the time provided cannot meet the time requirement of the user. Compared with the development efficiency of others, the method has the advantage of higher development efficiency.
From the standpoint of coordination difficulty: the business team may be developed across regions, and the interior of the business team in the same region is divided into a plurality of development groups, so that the coordination and communication cost among the development groups is very high, and the coordination across regions and development groups is difficult.
2. Difficulty in changing demand
After the code repetition rate becomes high, it is very difficult to change the existing functions or add new requirements.
Taking a recharging and paying function as an example, the same quota protection function is developed in different recharging channels, and after the quota protection function is changed, all repeatedly developed quota protection functions need to be modified and tested again, so that the problems that the recharging functions of part of channels are normal and part of channels have bugs (bugs) are easily caused by inconsistent modification or omission.
3. Fail to satisfy fast innovation and agile delivery
In a Model View Controller (MVC) architecture, the business process is cascaded by a long string of local interface or method calls, is cumbersome and lengthy, and is developed and maintained by one person. With the development and the change of the requirements of the service, the local code is continuously iterated and changed, finally, vertical function islands are formed, only the original developer understands the interface calling relationship and the function requirements, and once the original developer leaves the job or transfers to other project groups, the operation and the maintenance of the service flow become very difficult.
4. Poor isolation and usability of system errors
An error in any one module may cause a downtime in the overall system.
5. Long period for repairing on-line problem
Any on-line problem repair requires a full upgrade of the entire application system.
In order to overcome the technical defects, the service processing system provided in the embodiment of the present application uses a group of micro-services to construct an application program, different micro-services are independently deployed in different processes, different micro-services communicate through a lightweight interaction mechanism such as Remote Procedure Call (RPC) and HTTP, each micro-service can be independently expanded and expanded, and each micro-service defines a clear boundary. Different microservices may even be implemented in different programming languages and maintained by independent teams.
Compared with a single application development framework, the micro-service development framework of the service processing system provided by the embodiment of the application has the characteristics of controllable complexity, independent deployment, flexible technical type selection, fault-tolerant mechanism, integrated swagger, easiness in service expansion and the like, and also has a series of new functions of authority control, service monitoring, code generation, continuous integration, log system and the like, so that the development difficulty and time cost can be reduced for enterprises. The service processing system provided by the embodiment of the application also reserves a single sign-on module, so that a user can conveniently connect other systems. Therefore, the service processing system provided by the embodiment of the application is a micro-service development framework compatible with high efficiency and practicability, so that developers can be released from the underlying technology completely, only the business function modules of the developers need to be concerned, a high-cohesion and low-coupling micro-service application system can be established quickly, and the aims of development standardization, system modularization and application servitization are achieved.
The functional architecture of the service processing system provided in the embodiment of the present application may be as shown in fig. 8, and includes: foreground access 81, platform services 82, and storage 83.
The foreground access 81 comprises a foreground management portal 801, and the foreground management portal 801 can be realized by front-end micro-services, and provides a visual operation interface for a developer to use.
The platform service 82 includes: authentication 821, platform management 822, service management 823, system management 824, and development support 825.
Authentication 821: the method can be realized by authentication microservice, and comprises user authentication 8211 and interface authentication 8212, wherein the user authentication 8211 supports user identity authentication and controls access authority; interface authentication 8212 supports interface service authentication and controls calling authority.
Platform management 822: and basic management functions such as registration login, user management, organization management, role management, menu management, metadata management and the like are provided, and the user only needs to perform relevant configuration.
Service management 823: and service management functions such as service registration, service monitoring and service flow control are provided, and service operation is guaranteed.
System management 824: the system management functions of log management, cache management, service degradation and the like are provided, and the overall operation of the service processing system is guaranteed.
Development support 825: development auxiliary functions such as front-end code generation, document making, message center and the like are provided, and a development user can use the development auxiliary functions only by configuration; and provides code automatic construction functions.
Storage 83: and storing the micro-service development framework basic data. The storage function may be implemented based on a storage form such as a relational database 831, a cache 832, a Message Queue (MQ) 833, and the like.
The technical architecture of the service processing method provided by the embodiment of the present application is shown in fig. 9:
the Web module receives the HTTP request of the browser/client and forwards the HTTP request to the interface gateway module, and the interface gateway module carries out request forwarding processing on the received HTTP request.
The interface gateway module distributes the HTTP request to various service modules to complete the request call and returns the result to the Web module. Every calling of the interface gateway module needs to enter the authentication module, the request authority is not enough, or invalid requests are not passed to intercept, so that resources are protected.
Here, the different modules are different microservices, and each module is further described below.
The Web module 901: and the server is responsible for receiving an http request sent by a user from the browser client and returning a request processing result. Here, the framework of the present business process system is a front-end and back-end split design model.
Eureka module 902: the service registration module is mainly responsible for the registration function of each service module, and each service module can be connected together through the eureka registration center to realize mutual calling.
The Eureka module 902 includes two parts, Eureka a and Eureka B, so as to realize the backup of the Eureka module. When one hangs up, the service registration service may be provided through the other.
Here, the Spring Boot Admin may be built based on the Eureka module 902, so that the Eureka module monitors each micro-service through the Spring Boot Admin.
Interface gateway module 903: the client is registered in the Eureka module 902, receives an http request from the Web module 901, and distributes the http request to different service modules according to different types of traffic of the http request.
The authentication module 904: the Spring security oAuth2 and jwt technologies are used for realizing user identity authentication and resource control access calling.
The configuration service module 905: a distributed configuration center. In the microservice architecture, since a plurality of microservices are distributed, the configuration file of each microservice can be conveniently managed in a unified manner through the configuration service module 905, and can be updated in real time.
Storage resources module 906: a series of storage functions such as redis cache, database (e.g., MySQL), distributed file system (e.g., MQ), message queue, etc. are provided.
The function service module 907: in addition to the basic functional services that provide the service: besides management service, short message service and code generation service, other micro-service functions can be arbitrarily expanded in the function service module 907 based on automatic construction, so that compared with a single framework, the function easy to expand greatly improves development efficiency and reduces development period.
The function service module 907 and the Web module 901 interact with each other through a message bus 908.
The function service module 907 and the storage resource module 906 can store data through a persistent layer framework MyBatis. Among them, MyBatis supports customized SQL, stored procedures, and advanced mapping.
Different modules in the service processing system can be called through different protocols, such as: the Eureka module 902 calls the interface gateway module 903 through JSON, and the interface gateway module 903 calls the Eureka module 902 through httprentful, such as: the authentication module 904 calls the interface gateway module 903 through JSON, and the interface gateway module 903 calls the authentication module 904 through HTTP.
ELK (elastic search + Logstash + Kibana) can be integrated in the service processing system to realize the log statistical analysis of the service processing system.
The specific process of the authentication module 904 for user identity authentication and resource control access is shown in fig. 10:
1001, a client sends a login request carrying a user name and a password to an interface gateway module;
when a user logs in for the first time, a user name and a password are input, and the login request triggered at the moment carries the user name and the password.
here, the token may be jwt (JSON Web token) that securely transfers information between parties as a JSON object.
The service request may be a call API request or a resource request. When a client side initiates a service request, the authorization value in the request head of the service request is the generated character string of the JWT.
and comparing the token carried by the service request with the token obtained from the token storage module.
here, the service module corresponds to a business microservice.
Here, the service processing method provided by the embodiment of the application can ensure that a service processing system realized based on the micro-service is safer, and only one authorized login is required among a plurality of micro-services.
When a development user develops an application program through the service processing system provided by the embodiment of the application, the development user can rapidly construct own development application by using the micro-service application framework, submits a code to a remote warehouse after developing the application service, and jenkins acquires the code to automatically construct and package the code and pushes the code to a mirror image warehouse, so that one-click construction is completed. Meanwhile, the access to the PaaS platform can be supported, and automatic deployment and release are carried out by means of platform elastic computing service.
A specific flow of software release performed by the micro service application development platform based on the service processing system provided in the embodiment of the present application is shown in fig. 11:
1. a development user downloads codes on the micro-service application development platform, codes can be compiled according to the needs of the development user to establish services or front-end service modules, the codes are submitted to the micro-service application development platform, and the micro-service application development platform of the PaaS platform provides one-click compiling, publishing and running.
2. In a PaaS platform, a research and development construction flow line obtains codes, automatically constructs and packs the codes to construct service jenkins, and pushes the service jenkins to a mirror image warehouse, so that one-click construction is completed.
3. The PaaS platform deploys and runs resources allocated by the elastic computing service.
Meanwhile, according to the micro-service application development platform provided by the embodiment of the application, the developed micro-service can be deployed on the PaaS platform only by simple configuration, and is in the same environment with the development platform. The service management of the container is provided by the PaaS platform, and the management and control of the micro-service are provided by the development platform, so that a complete operation chain is formed. And each micro-service can be independently modified, constructed and deployed, and has no influence on other micro-services.
The platform provides a standard development framework for generating the micro service, shields complex technical details, and research personnel only need to pay attention to writing of business codes and micro service configuration. The micro-service framework of the platform strengthens the modular structure of the system, each service module is a unit which can be independently deployed and operated under the framework, and clear boundaries are defined among the modules in the form of message driven APIs. Meanwhile, the platform packages a service register, a service finder, a service provider list and a service registration center for the micro-service, and has the functions of code automatic generation, service monitoring and the like. The micro-service development framework provided by the platform can quickly establish a high-cohesion and low-coupling micro-service application, and the aims of development standardization, system modularization and application servitization are achieved.
The service processing system provided by the embodiment of the application is a micro-service development framework and has the following technical characteristics:
(1) the method can monitor the service running state, and is convenient for developers to find out abnormal conditions of the service in time.
(2) And dynamically monitoring and recording the service calling interface, and taking the recording result as the basis for the application program to actually call the platform API.
(3) And the on-line swagger on-line test environment is provided, so that the tester is more convenient.
(4) The background management system provides automatic code generation, can simply generate classes such as controller, service, mapper and the like, and provides some common methods for a developer to call. This greatly reduces the need for developers to write control, service, mapper, etc. duplicate code when expanding new microservice code.
(5) And a monitoring function is provided, so that the deployment process log after the developer submits the code can be monitored, and the problem positioning of the developer is facilitated.
It can be seen that the application has the following technical effects:
1. easy development and maintenance, fast start-up: a developer only pays attention to a specific service function when using the micro-service development framework, so that the micro-service development framework has clear service, small code amount and quick start. Developing and maintaining a single microservice is relatively simple compared to a monolithic architecture. The whole application is constructed by a plurality of micro-services, so that the whole application can be maintained in a controllable state.
2. Local modifications are easy to deploy: the single application architecture is modified, the whole application needs to be redeployed, errors are easy to occur, and the micro-service development framework solves the problem. Generally, for a certain micro-service modification, only the service needs to be redeployed, and the error probability is greatly reduced.
3. Stretching as required: and fine granularity expansion can be realized according to requirements. For example, when a micro service in the system encounters a bottleneck, the characteristics of the micro service can be combined to increase the memory, upgrade the CPU or increase the nodes.
Fig. 12 is a schematic diagram of a hardware device of a service processing apparatus according to an embodiment of the present application, and as shown in fig. 12, the service processing apparatus 1200 includes: a processor 1201, at least one communication bus 1202, a user interface 1203, at least one external communication interface 1204 and a memory 1205. Wherein the communication bus 1202 is configured to enable connective communication between such components. The external communication interface 1204 may include a standard wired interface and a wireless interface, among others.
The processor 1201 is configured to implement the steps in the service processing method provided in the foregoing embodiment when the computer program is run.
The method disclosed by the embodiment of the application can be applied to the processor 1201, or implemented by the processor 1201. The processor 1201 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 1201. The processor 1201 described above may be a general purpose processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 1201 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located on a storage medium located in the memory 1205, and the processor 1201 reads the information from the memory 1205 and performs the steps of the aforementioned methods in conjunction with its hardware.
Here, it should be noted that: the description of the above device embodiment is similar to the description of the above method, and has the same beneficial effects as the method embodiment, and therefore, the description thereof is omitted. For technical details that are not disclosed in the terminal embodiment of the present application, those skilled in the art should refer to the description of the method embodiment of the present application for understanding, and for the sake of brevity, will not be described again here.
In an exemplary embodiment, the present application further provides a storage medium, which may be a computer-readable storage medium, for example, a memory 1205 that stores a computer program, and the computer program may be processed by the processor 1201 to implement the steps of the foregoing method. The computer readable storage medium may be Memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface Memory, optical disk, or CD-ROM.
The embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is processed by a processor to implement the steps in the service processing method provided in the foregoing embodiment.
Here, it should be noted that: the above description of the storage medium embodiment is similar to the above description of the method, and has the same beneficial effects as the method embodiment, and therefore, the description thereof is omitted. For technical details that are not disclosed in the terminal embodiment of the present application, those skilled in the art should refer to the description of the method embodiment of the present application for understanding, and for the sake of brevity, will not be described again here.
It is to be appreciated that the memory (memory 1205) of the embodiments of the application can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. Among them, the nonvolatile Memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic random access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memories described in the embodiments of the present application are intended to comprise, without being limited to, these and any other suitable types of memory.
The above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application.
Claims (12)
1. A service processing method is applied to a service processing system, wherein the service processing system is composed of micro-services, and the micro-services include: interface gateway microservice, authentication microservice and business microservice, the method comprising:
receiving a login request at the interface gateway microservice, and sending an account and a password carried by the login request to an authentication microservice;
after the authentication microservice determines that the account and the password pass authentication, distributing a token for the account;
receiving a service request corresponding to the account at the interface gateway micro-service, acquiring a token carried by the service request and a token distributed for the account, determining that the token carried by the service request is the same as the token distributed for the account, and sending the service request to the service micro-service;
and processing the service request at the service microservice.
2. The method of claim 1, wherein sending the service request to the service microservice comprises:
determining the service type of the received service request, and determining a target service microservice corresponding to the service type in the service microservices;
correspondingly, the service request is processed in the target service microservice.
3. The method of claim 1, wherein the microservice further comprises: the service registers for the micro-service,
and registering the micro service in the service, registering the micro service, and constructing an association relation between different micro services.
4. The method of claim 3, wherein the microservice comprises a first microservice and a second microservice, the first microservice and the second microservice being different microservices in the business processing system; the method further comprises the following steps:
after the first micro service processes the service request, sending a calling message to the service registration micro service;
registering micro service in the service, determining address information of the second micro service according to the first micro service, and returning the address information of the second micro service to the first micro service;
and calling the second micro service based on the address information of the second micro service in the first micro service, and sending the processed service request to the called second micro service.
5. The method of claim 4, wherein the invoking the second micro service based on the address information of the second micro service and sending the processed service request to the invoked second micro service comprises:
based on the address information, the message drives an interface between the first micro service and the second micro service, the second micro service is called based on the driven interface, and the processed service request is sent to the called second micro service based on the driven interface.
6. The method of claim 1, wherein the microservice further comprises: a front-end microservice, the method further comprising:
and receiving the service request at the front-end micro service, and outputting a processing result of the target service micro service to the service request.
7. The method of claim 6, further comprising:
receiving the token distributed for the account at the front-end micro service, packaging the token distributed for the account in the service request, and sending the service request packaged with the token distributed for the account to the interface gateway micro service;
and receiving a processing result of the business request by the business micro service at the interface gateway micro service, and sending the processing result to the front-end micro service.
8. The method of any of claims 1 to 7, wherein the microservice further comprises: a service flow control microservice, the method further comprising:
and monitoring the running micro-services in the service flow control micro-services, and correspondingly allocating resources according to the priority of each running micro-service.
9. The method of claim 8, further comprising:
and detecting the total resource usage used by the running micro-service in the service flow control micro-service, and adjusting the priority of the running micro-service when the total resource usage is greater than a set resource usage threshold.
10. A business processing system is characterized in that the business processing system is composed of micro-services, wherein the micro-services comprise interface gateway micro-services, authentication micro-services and business micro-services; wherein,
the interface gateway micro-service is used for receiving a login request and sending an account and a password carried by the login request to the authentication micro-service;
the authentication microservice is used for distributing tokens to the account after the account and the password are authenticated;
the interface gateway micro-service is further configured to receive a service request corresponding to the account, acquire a token carried by the service request and a token allocated to the account, determine that the token carried by the service request is the same as the token allocated to the account, and send the service request to the service micro-service;
and the service microservice processes the service request.
11. A transaction device comprising a processor and a memory for storing a computer program operable on the processor; wherein the processor is configured to execute the steps in the service processing method according to any one of claims 1 to 9 when the computer program is executed.
12. A storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the service processing method of any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910731249.2A CN112350978A (en) | 2019-08-08 | 2019-08-08 | Service processing method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910731249.2A CN112350978A (en) | 2019-08-08 | 2019-08-08 | Service processing method, system, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112350978A true CN112350978A (en) | 2021-02-09 |
Family
ID=74366870
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910731249.2A Withdrawn CN112350978A (en) | 2019-08-08 | 2019-08-08 | Service processing method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112350978A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113472794A (en) * | 2021-07-05 | 2021-10-01 | 福州数据技术研究院有限公司 | Multi-application system authority unified management method based on micro-service and computer readable storage medium |
| CN113542217A (en) * | 2021-06-07 | 2021-10-22 | 广发银行股份有限公司 | Service subscription system |
| CN113704755A (en) * | 2021-07-13 | 2021-11-26 | 奇安信科技集团股份有限公司 | File detection method, file detection device, electronic equipment, program and storage medium |
| CN114189384A (en) * | 2021-12-14 | 2022-03-15 | 中国建设银行股份有限公司 | Service processing method, device, equipment and storage medium |
| CN114327389A (en) * | 2021-12-24 | 2022-04-12 | 商派软件有限公司 | Application management method, account management plug-in and application management system |
| CN114463135A (en) * | 2021-12-24 | 2022-05-10 | 上海金仕达软件科技有限公司 | Stock right management method, system, device, equipment, storage medium and program product |
| CN114816791A (en) * | 2022-04-18 | 2022-07-29 | 北京有竹居网络技术有限公司 | Data service providing method, device, medium and electronic equipment |
| CN118586872A (en) * | 2024-08-05 | 2024-09-03 | 国网山东省电力公司滨州供电公司 | Micro-service-based power grid business center management and control system, method, equipment and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150281225A1 (en) * | 2014-03-27 | 2015-10-01 | Microsoft Corporation | Techniques to operate a service with machine generated authentication tokens |
| CN108901022A (en) * | 2018-06-28 | 2018-11-27 | 深圳云之家网络有限公司 | A kind of micro services universal retrieval method and gateway |
| CN109327477A (en) * | 2018-12-06 | 2019-02-12 | 泰康保险集团股份有限公司 | Authentication method, device and storage medium |
| CN109743163A (en) * | 2019-01-03 | 2019-05-10 | 优信拍（北京）信息科技有限公司 | Purview certification method, apparatus and system in micro services framework |
-
2019
- 2019-08-08 CN CN201910731249.2A patent/CN112350978A/en not_active Withdrawn
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150281225A1 (en) * | 2014-03-27 | 2015-10-01 | Microsoft Corporation | Techniques to operate a service with machine generated authentication tokens |
| CN108901022A (en) * | 2018-06-28 | 2018-11-27 | 深圳云之家网络有限公司 | A kind of micro services universal retrieval method and gateway |
| CN109327477A (en) * | 2018-12-06 | 2019-02-12 | 泰康保险集团股份有限公司 | Authentication method, device and storage medium |
| CN109743163A (en) * | 2019-01-03 | 2019-05-10 | 优信拍（北京）信息科技有限公司 | Purview certification method, apparatus and system in micro services framework |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113542217A (en) * | 2021-06-07 | 2021-10-22 | 广发银行股份有限公司 | Service subscription system |
| CN113542217B (en) * | 2021-06-07 | 2023-05-26 | 广发银行股份有限公司 | Service subscription system |
| CN113472794A (en) * | 2021-07-05 | 2021-10-01 | 福州数据技术研究院有限公司 | Multi-application system authority unified management method based on micro-service and computer readable storage medium |
| CN113472794B (en) * | 2021-07-05 | 2023-08-15 | 福州数据技术研究院有限公司 | Multi-application system authority unified management method based on micro-service and storage medium |
| CN113704755A (en) * | 2021-07-13 | 2021-11-26 | 奇安信科技集团股份有限公司 | File detection method, file detection device, electronic equipment, program and storage medium |
| CN114189384A (en) * | 2021-12-14 | 2022-03-15 | 中国建设银行股份有限公司 | Service processing method, device, equipment and storage medium |
| CN114189384B (en) * | 2021-12-14 | 2024-04-02 | 中国建设银行股份有限公司 | Service processing method, device, equipment and storage medium |
| CN114327389A (en) * | 2021-12-24 | 2022-04-12 | 商派软件有限公司 | Application management method, account management plug-in and application management system |
| CN114463135A (en) * | 2021-12-24 | 2022-05-10 | 上海金仕达软件科技有限公司 | Stock right management method, system, device, equipment, storage medium and program product |
| CN114816791A (en) * | 2022-04-18 | 2022-07-29 | 北京有竹居网络技术有限公司 | Data service providing method, device, medium and electronic equipment |
| CN118586872A (en) * | 2024-08-05 | 2024-09-03 | 国网山东省电力公司滨州供电公司 | Micro-service-based power grid business center management and control system, method, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112350978A (en) | Service processing method, system, device and storage medium | |
| US11921703B2 (en) | Dag based methods and systems of transaction processing in a distributed ledger | |
| CN113169952B (en) | Container cloud management system based on block chain technology | |
| US8572706B2 (en) | Policy engine for cloud platform | |
| EP2313833B1 (en) | Service integration platform system and method for internet services | |
| US20120311157A1 (en) | Integrated information technology service management for cloud resources | |
| US10798218B2 (en) | Environment isolation method and device | |
| US9507927B2 (en) | Dynamic identity switching | |
| AU2016203802A1 (en) | Integrated information technology service management for cloud resources | |
| US11140147B2 (en) | SAML SSO UX improvements | |
| CN112543169B (en) | Authentication method, authentication device, terminal and computer readable storage medium | |
| CN112149079A (en) | Planning review management platform based on micro-service architecture and user access authorization method | |
| US20230061228A1 (en) | Managing shared applications at the edge of a content delivery network | |
| US20180052671A1 (en) | System and method to control hybrid deployment of an application | |
| CN114168179B (en) | Micro-service management method, micro-service management device, computer equipment and storage medium | |
| CN115086166A (en) | Computing system, container network configuration method, and storage medium | |
| CN116932251B (en) | System integration method and system based on micro front end | |
| CN117850771A (en) | Business application development platform, method and storage medium for web service | |
| CN115604344B (en) | Micro-service current limiting method and device | |
| US8353013B2 (en) | Authorized application services via an XML message protocol | |
| CN112929195A (en) | Service system, method executed by service system, processing apparatus, and storage medium | |
| WO2024066018A1 (en) | Method and apparatus for cross-chain calling of smart contracts | |
| CN116126554A (en) | Cross-chain calling method and device for intelligent contracts | |
| CN116827925A (en) | Application management method and device, storage medium and electronic equipment | |
| CN115665141A (en) | Cross-chain calling method and device for intelligent contract |
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: 20210209 |
|
| WW01 | Invention patent application withdrawn after publication |