Service identifier configuration method and device based on micro-service architecture, equipment and medium

Abstract

The invention relates to the field of data verification and financial science and technology, and discloses a service identification configuration method, device and equipment based on a micro-service architecture and a medium, identification management and control and configuration functions are separated from a flow of a service system, identification management and control are built on an independent micro-service application, and the service management and control efficiency is improved. According to the method, verification of various different business identifiers is realized by calling the identifier management and control micro-service in the business system flow circulation logic, unified management and control of the identifiers are realized, real-time adjustment and updating of the identifiers are further carried out in the identifier management and control micro-service, identifier configuration is rapidly carried out, normal circulation logic of the business system is not influenced, and the business system flow circulation efficiency is improved. The method reduces the cost of identifier management and control, and solves the technical problems of scattered identifiers, difficulty in unified management and maintenance, difficulty in identifier adjustment, easy influence on the stability and performance of the system, and lack of flexibility in the existing identifier management and control.

Description

Technical Field

[0001] The present application relates to the fields of data verification and financial technology, and in particular to a business identification configuration method, device, equipment and medium based on a microservice architecture. Background Art

[0002] In the process of credit approval and loan review for public credit, banks and other financial institutions face complex risk management challenges. In order to ensure the security and compliance of loans, financial institutions need to conduct strict review of counterparties, which usually involves checking various lists, such as blacklists, graylists, and watchlists. These lists may contain individuals or companies with risk information such as bad credit records, legal proceedings, fraud, etc.

[0003] In traditional corporate credit systems, list control identifiers are usually embedded into the system's backend processes through programming. Although this approach can achieve basic list control functions, it also brings a series of problems:

[0004] Dispersed identification: Due to the diversity of corporate credit business scenarios, the applicable list control identification is also different. This results in the identification being dispersed in different business scenarios and code modules, making it difficult to manage and maintain them uniformly.

[0005] Difficulty in adjustment: When regulatory policies change or business needs are adjusted, the existing list control logo needs to be modified. Since the logo is closely tied to the system process, any change may affect the stability and performance of the entire system, so the transformation cost is high and the risk is high.

[0006] High maintenance cost: As the business develops, new list control identifiers need to be added and old identifiers need to be updated or deleted. Such frequent changes require the IT team to invest a lot of manpower and time to sort out and modify the code.

[0007] Lack of flexibility: Hard-coded identifiers lack flexibility and are difficult to adapt to rapidly changing market environments and regulatory requirements. In some cases, you may need to respond quickly to new business needs or regulatory changes, but traditional system architectures limit this flexibility. Summary of the invention

[0008] The present application provides a business identification configuration method, device, equipment and medium based on a microservice architecture, which solves the technical problems of existing identification management and control, such as identification dispersion, difficulty in unified management and maintenance, difficulty in identification adjustment, easy impact on system stability and performance, and lack of flexibility.

[0009] In view of this, the first aspect of the present application provides a service identification configuration method based on a microservice architecture, the method comprising:

[0010] When the business system performs business identification verification, the business system transmits the target parameters contained in the business identification to the identification management and control microservice;

[0011] The identification management and control microservice performs verification according to the business identification and the target parameters, and transmits the generated verification result to the business system.

[0012] A second aspect of the present application provides a service identification configuration device based on a microservice architecture, the device comprising:

[0013] A processing unit, configured to transmit the target parameters contained in the business identifier to the identifier management and control microservice when the business system performs business identifier verification;

[0014] A verification unit is used for the identification management and control microservice to verify the business identification and the target parameters, and transmit the generated verification result to the business system.

[0015] A third aspect of the present application provides a service identification configuration device based on a microservice architecture, the device comprising a processor and a memory:

[0016] The memory is used to store program code and transmit the program code to the processor;

[0017] The processor is used to execute the steps of the method for business identification configuration based on microservice architecture as described in the first aspect above according to the instructions in the program code.

[0018] A fourth aspect of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store program code, and the program code is used to execute the method described in the first aspect above.

[0019] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0020] In the present application, a business identification configuration method, device, equipment and medium based on a microservice architecture are provided, which separates the identification control and configuration functions from the process of the business system, builds the identification control on an independent microservice application, and verifies various business identifications by calling the identification control microservice in the process flow logic of the business system, thereby realizing unified identification control. Furthermore, the identification is adjusted and updated in real time in the identification control microservice, and the identification is configured quickly without affecting the normal flow logic of the business system, thereby reducing the cost of identification control, and solving the technical problems of existing identification control, such as identification dispersion, difficulty in unified management and maintenance, difficulty in identification adjustment, easy impact on system stability and performance, and lack of flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 This is a schematic diagram of an application environment of a service identification configuration method based on a microservice architecture in an embodiment of the present application;

[0022] Figure 2 A method flow chart of a method for configuring a service identifier based on a microservice architecture in an embodiment of the present application;

[0023] Figure 3 This is a structural diagram of a service identification configuration device based on a microservice architecture in an embodiment of the present application;

[0024] Figure 4 This is a structural diagram of a business identification configuration device based on a microservice architecture in an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0026] The business identification configuration method based on microservice architecture provided in this application can be applied in Figure 1 In an application environment, the client communicates with the server through a network. The server can separate the identification management and configuration functions from the process of the business system, build the identification management on an independent microservice application, and verify various business identifications by calling the identification management microservice in the process flow logic of the business system, so as to realize the unified management and control of identification. Furthermore, the server can adjust and update the identification in real time in the identification management microservice through the client, and quickly configure the identification without affecting the normal flow logic of the business system, thereby reducing the cost of identification management and control, and solving the technical problems of the existing identification management, such as the scattered identification, difficulty in unified management and maintenance, difficulty in identification adjustment, easy impact on the stability and performance of the system, and lack of flexibility. Among them, the client can be but not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices. The server can be implemented with an independent server or a server cluster consisting of multiple servers. The present application is described in detail below through specific embodiments.

[0027] For easier understanding, see Figure 2 , Figure 2 This is a method flow chart of a method for configuring a business identifier based on a microservice architecture in an embodiment of the present application. Figure 2 As shown, specifically:

[0028] S201. When the business system performs business identification verification, the business system transmits the target parameters contained in the business identification to the identification management and control microservice;

[0029] It should be noted that the embodiment of the present application describes the interaction process between the business system and the identity management and control microservice.

[0030] Business ID verification trigger:

[0031] When a business system performs specific operations, such as user form submission, transaction processing, or data import, it needs to be verified based on the preset business identifier.

[0032] Determination of target parameters:

[0033] The business system identifies and determines the parameters that need to be verified, which are related to the business identifier, such as the user's credit score, transaction amount, account status, etc.

[0034] Parameter transmission:

[0035] The business system sends these target parameters to the identity management microservice through a network request.

[0036] S202. The identification control microservice performs verification according to the business identification and target parameters, and transmits the generated verification result to the business system.

[0037] It should be noted that the verification:

[0038] After receiving the parameters, the identity management microservice performs logical judgment and verification based on the preset business identity, such as checking whether the user meets the credit standards.

[0039] Generate verification results:

[0040] The identity control microservice generates a verification result based on the result of the identity execution. The result may be "pass", "fail", or other business-related responses.

[0041] Result transmission:

[0042] The identity control microservice returns the verification results to the business system.

[0043] Business Decisions:

[0044] The business system performs subsequent operations based on the verification results. For example, if the verification result is "passed", the transaction processing continues.

[0045] Suppose an online banking platform needs to decide whether to approve a loan application based on the user's credit score.

[0046] User applies for loan:

[0047] Users submit loan applications through the business system and provide personal information.

[0048] Business system processing application:

[0049] The business system collects user information, including credit scores, income levels, etc.

[0050] Call the identity control microservice:

[0051] The business system sends the user's credit score as a target parameter to the identity management microservice.

[0052] The identity control microservice performs verification:

[0053] After receiving the user's credit score, the identity control microservice verifies it based on the loan approval identifier (for example, a credit score greater than 650 points will be approved).

[0054] Generate and return verification results:

[0055] If the user's credit score meets the identification, the identification control microservice returns an "approved" result;

[0056] If not satisfied, a "reject" result is returned.

[0057] Business system execution decision:

[0058] If the result is "approved", the business system continues to process loan issuance;

[0059] If the result is "rejected", the business system rejects the loan application and notifies the user.

[0060] Through this architecture, business systems can flexibly use preset business identifiers to make decisions while maintaining central management and updating of the identifiers.

[0061] Furthermore, it also includes:

[0062] Before executing the business identification verification, the business system receives a user's configuration request for the business identification through a user interface, and the user interface includes an identification editor;

[0063] Through the preset configuration management tool, the preset identifiers contained in the identity control microservice are updated or new business identifiers are added according to the configuration request.

[0064] It should be noted that the embodiment of the present application describes the process of how the business system receives a user's request for configuring a business identifier and updates or adds a new business identifier.

[0065] The user interface provides a logo editor:

[0066] The business system provides a user interface (UI) including an identity editor that allows users (such as administrators, business analysts, etc.) to define, edit, and delete business identities.

[0067] Receive configuration request:

[0068] The Identity Editor is used by users to submit configuration requests for business identities, such as creating a new identity, modifying an existing identity, or deleting an identity.

[0069] Configuration Management Tools:

[0070] The business system is connected to a configuration management tool, which is responsible for managing the configuration information of the business identity.

[0071] Handling configuration requests:

[0072] The configuration management tool receives configuration requests from the user interface and updates or adds new business identifiers based on the requests.

[0073] Logo updates:

[0074] If the request is to update an existing identity, the configuration management tool looks for and modifies the corresponding identity configuration.

[0075] New business logo:

[0076] If the request is for a new identity, the configuration management tool creates a new identity configuration in the identity repository.

[0077] Synchronize to the identity control microservice:

[0078] Updated or newly added identity configurations will be synchronized to the identity control microservice so that the microservice can use the latest business identity for verification.

[0079] Suppose an e-commerce platform needs to dynamically adjust discount labels based on user shopping behavior.

[0080] Administrator login:

[0081] The platform administrator logs in to the business system user interface.

[0082] To access the Identity Editor:

[0083] Administrators access the built-in logo editor to create a new offer logo.

[0084] To configure a new identity:

[0085] In the logo editor, the administrator defines a new logo: "If the user shopped during the weekend and the purchase amount exceeded 100 yuan, a 10% discount will be automatically applied."

[0086] Submit a configuration request:

[0087] The administrator submits a configuration request for a new identity through the user interface.

[0088] Configuration management tools handle requests:

[0089] The configuration management tool receives the request, creates a new business identity configuration, and stores it in the identity library.

[0090] Synchronize to the identity control microservice:

[0091] The new identity configuration is pushed to the identity control microservice, which loads and prepares to execute the new identity.

[0092] Execute the new logo:

[0093] The identity control microservice begins to apply the new identity to the user's consumption behavior, and eligible users will receive discounts.

[0094] In this way, business systems can flexibly adapt to changing business needs while ensuring consistency and maintainability of identification.

[0095] Furthermore, it also includes:

[0096] The identity control microservice generates a monitoring report based on the verification results of the business identity;

[0097] When the monitoring report contains verification failure results that exceed the preset threshold, the identification control microservice marks the business ID and issues an alarm.

[0098] It should be noted that the embodiment of the present application describes the process of how the identity management and control microservice generates a monitoring report and triggers an alarm when the verification failure exceeds a preset threshold.

[0099] Verification execution:

[0100] The identity control microservice verifies incoming business requests based on the business identity.

[0101] Collect the verification results:

[0102] The microservice records the result of each validation, including success or failure.

[0103] Generate monitoring report:

[0104] Generate monitoring reports regularly (such as daily, weekly) or in real time to summarize the verification results.

[0105] Setting the threshold:

[0106] Set preset thresholds for different types of verification failures, such as a failure rate of 5% as the threshold.

[0107] Analysis and monitoring reports:

[0108] Analyze the data in the monitoring reports to determine if any of the indicators have a failure rate above the preset threshold.

[0109] Marking business logo:

[0110] If the verification failure results exceed the threshold, the microservice will automatically mark the business identity.

[0111] Triggering the alarm:

[0112] Trigger an alarm mechanism to notify relevant personnel or systems so that actions can be taken.

[0113] Alarm method:

[0114] Alerts can be communicated via email, SMS, system notifications, or by integrating a third-party alert system.

[0115] Responsive and adaptable:

[0116] Relevant personnel analyze and respond to the problem based on the alarm information, which may require adjusting business identification or repairing the underlying problem.

[0117] Suppose a financial institution uses an identity control microservice to verify whether credit card transactions are fraudulent.

[0118] Transaction verification:

[0119] Whenever a credit card transaction occurs, the identity control microservice will verify it based on the preset anti-fraud identity.

[0120] Record the results:

[0121] The microservice records the verification results of each transaction and marks it as "normal" or "fraudulent".

[0122] Generate daily report:

[0123] The identity control microservice generates a monitoring report every day, summarizing the verification results of all transactions.

[0124] Daily Analysis:

[0125] In the monitoring report, the microservice analyzes the proportion of "fraudulent" results.

[0126] Setting the threshold:

[0127] The preset threshold is set at no more than 1% of total transactions being considered as “fraudulent” results.

[0128] Detection exceeds the standard:

[0129] If the monitoring report shows that the proportion of "fraud" results exceeds 1%, the microservice will mark the relevant anti-fraud logo.

[0130] Triggering the alarm:

[0131] The microservice sends alerts via email to risk management and IT support teams.

[0132] Investigation and Response:

[0133] The cause of the alert is investigated and may require updating anti-fraud identification or enhancing security measures.

[0134] In this way, the identity control microservice can detect potential problems in a timely manner and notify relevant personnel to take measures, thereby improving the stability and security of the system.

[0135] Furthermore, it also includes:

[0136] When there are two or more business systems, the identity control microservice assigns corresponding identity access rights to each business system;

[0137] If the business system transmits the target parameters contained in the business identifier in the non-identification access permission to the identity control microservice, the identity control microservice returns a prompt of no permission to the business system.

[0138] It should be noted that the embodiments of the present application describe how the identity control microservice manages and limits access rights to business identities in a multi-business system environment.

[0139] Business system identification:

[0140] Each business system needs to be uniquely identified when interacting with the identity management microservice, which may be through a system ID, API key, or other authentication mechanism.

[0141] Assign access permissions:

[0142] The identity control microservice assigns access rights to specific business identities to each business system based on business security policies and requirements.

[0143] Permission storage:

[0144] Access permission information is stored in the permission configuration database or access control list (ACL) of the identity management microservice.

[0145] Permission verification:

[0146] When a business system sends a business identity verification request, the identity control microservice verifies whether the request complies with the business system's access rights.

[0147] No permission prompt:

[0148] If a business system attempts to access an unauthorized business identity, the identity management microservice will reject the request and return an error message indicating that the system does not have permission.

[0149] Security Audit:

[0150] All access attempts, authorized or unauthorized, are recorded in the security audit log to facilitate issue investigation and compliance checks.

[0151] Dynamic permission management:

[0152] When necessary, administrators can dynamically adjust the access permissions of business systems, such as updating the ACL through the management interface.

[0153] Suppose a company has two business systems: one is the customer relationship management system (CRM) and the other is the order processing system (OPS).

[0154] Permission allocation:

[0155] CRM is authorized to access business identifiers related to customer data, such as "customer credit score verification."

[0156] OPS is authorized to access business identifiers related to order processing, such as "order amount limit verification".

[0157] Business system request:

[0158] The CRM sends a request to the identity management microservice with a target parameter containing the customer's credit score, requesting a "customer credit score verification".

[0159] OPS sends a request containing the target parameter of the order amount to the identity control microservice, requesting "order amount limit verification".

[0160] Permission verification:

[0161] The identity control microservice checks the CRM request, confirms that it has access to the "Customer Credit Score Verification" identity, processes the request and returns the result.

[0162] The identity control microservice checks the OPS's request, confirms that it has access to the "Order Amount Limit Verification" identity, processes the request, and returns the result.

[0163] Unauthorized request:

[0164] OPS attempts to send a request with a target parameter that includes the customer's credit score, an indication that it does not have permission to access.

[0165] The identity control microservice detects an unauthorized request, refuses to process it, and returns an "unauthorized" error message.

[0166] Audit records:

[0167] All requests, including rejected unauthorized requests, are recorded in the audit log for subsequent review.

[0168] In this way, the identity management microservice can ensure that each business system can only access its authorized business identity, thereby enhancing the security and reliability of the system.

[0169] Furthermore, when the business system performs business identification verification, the business system transmits the target parameters contained in the business identification to the identification management and control microservice and further includes:

[0170] If the preferred service instance of the identity control microservice cannot respond to the verification request for the business identity in the business system, the verification request will be forwarded to the alternative service instance until all alternative service instances fail to respond or there is a responding alternative service instance;

[0171] The identification control microservice uses the circuit breaker mode to cut off the preferred service instance or alternative service instance that fails to respond.

[0172] It should be noted that the Circuit Breaker Pattern is a software design pattern used to handle unstable components or services in the system. When a service or component fails, the Circuit Breaker Pattern prevents the system from constantly trying to perform operations that may fail, thereby protecting the entire system from failures and improving system stability and availability.

[0173] The core idea of ​​the circuit breaker pattern is to imitate the working principle of the circuit breaker in the power system: when a fault is detected, the circuit breaker will cut off the current to prevent the fault from spreading; when the fault is cleared, the circuit breaker can restore the circuit and restore the system to normal operation.

[0174] The circuit breaker mode usually includes the following states:

[0175] Closed: This is the initial state of the circuit breaker. The system is running normally and requests are sent directly to the service or component.

[0176] Open state: When the number of failed requests reaches a preset threshold within a certain period of time, the circuit breaker will open to prevent more requests from being sent to the service.

[0177] Half-Open: After the circuit breaker is opened for a period of time, the system will try to send requests in a limited manner to test whether the service has returned to normal.

[0178] The circuit breaker pattern is particularly useful in a microservice architecture because it can help prevent the failure of a single service from causing the collapse of the entire system. It is often used with a service degradation strategy to provide an alternative handling method to ensure that users can still get some services when the service is unavailable.

[0179] This embodiment describes how to perform a service instance failover when the preferred service instance of the identity control microservice is unavailable during the business identity verification process, and how to use the circuit breaker pattern to prevent the spread of system failures.

[0180] Role definition for a service instance:

[0181] Preferred service instance: usually refers to the service instance that is primarily responsible for processing business requests.

[0182] Alternative service instance: refers to the service instance used to take over business requests when the preferred instance is unavailable.

[0183] Failover mechanism:

[0184] When the business system sends a business identity verification request to the preferred instance of the identity control microservice, and the preferred instance cannot process the request, the system needs to be able to automatically forward the request to the alternative instance.

[0185] Order and health check of candidate instances:

[0186] The candidate instances can have a priority order, and based on the results of the health check, the system decides which candidate instance to forward the request to.

[0187] Request forwarding:

[0188] If the preferred instance does not respond within a certain period of time, the system automatically forwards the request to the alternative instance.

[0189] Circuit Breaker Pattern:

[0190] If the number of consecutive failures of the preferred instance or the alternative instance reaches a certain threshold, the circuit breaker is triggered, cutting off calls to these instances to prevent the system from overloading.

[0191] Recovery of a failed instance:

[0192] After a period of time, the system will try to reestablish a connection with the failed service instance. If successful, the circuit breaker is closed and the service instance rejoins the service pool.

[0193] Notifications and Logging:

[0194] When failover and circuit breaker actions occur, the system records corresponding logs and notifies the operation and maintenance team.

[0195] Suppose an e-commerce platform uses a logo control microservice to verify whether the user's purchase behavior meets the promotion logo.

[0196] The business system sends a request:

[0197] After the user places an order, the business system of the e-commerce platform sends the order information to the identity management and control microservice for verification.

[0198] Preferred instance failure:

[0199] The preferred service instance might be unable to respond to the request in a timely manner due to overloading or internal errors.

[0200] Failover:

[0201] The system detects that the preferred instance is unresponsive and automatically forwards the request to the alternate instance.

[0202] Alternative instance processing:

[0203] The alternative instance receives the forwarded request, processes it successfully, and returns the verification result to the e-commerce platform.

[0204] Circuit breaker tripping:

[0205] If the alternative instance also fails or takes too long to respond, the circuit breaker is triggered, cutting off calls to the preferred instance and the alternative instance.

[0206] Fault logging and notification:

[0207] The system records the details of the failure instance and notifies the operations team for further investigation and remediation.

[0208] System Recovery:

[0209] After the failed service instance is restored, the circuit breaker is closed and the service instance rejoins the service pool, ready to receive new requests.

[0210] In this way, identity control microservices can improve the availability and stability of the system and maintain service continuity even when problems occur in some service instances.

[0211] Furthermore, after updating the preset identifier contained in the identifier control microservice or adding a new business identifier through the preset configuration management tool according to the configuration request, it also includes:

[0212] The identity control microservice performs a grayscale release of the preset identity or the newly added business identity after the identity update, and determines whether to fully execute the preset identity or the newly added business identity after the identity update based on the grayscale release result;

[0213] The identity control microservice performs a comparison test on the preset identity or the newly added business identity after the identity update, and determines whether to fully execute the preset identity or the newly added business identity after the identity update based on the comparison test results.

[0214] It should be noted that Canary Releases is a software release strategy used to gradually promote new versions of applications or services to the user group. This approach can reduce the impact on all users when a new version introduces problems, allowing real-time testing and evaluation of new versions before wider deployment. Its key features include:

[0215] Phased deployment: The new version is first deployed to a small number of users, usually internal employees or testers, and then the percentage of users is gradually increased.

[0216] Traffic splitting: Traffic in the production environment is split, with some users being directed to the new version while other users continue to use the old version.

[0217] A / B testing (also known as split testing or comparison testing) is a statistical method used to compare the performance of two or more versions of a web page, application, or other thing to determine which version is more effective. A / B testing is often used to test different designs, functions, layouts, algorithms, etc. to optimize user experience and increase conversion rates. Its key features include:

[0218] Control group and experimental group: In A / B testing, there are usually two versions of a page or application: the control group (version A) and the experimental group (version B). The control group is the current standard or baseline version, while the experimental group is the version with changes.

[0219] Random Assignment: Users are randomly assigned to a control group or an experimental group to ensure the validity of the test results.

[0220] Key Performance Indicators (KPIs): Identify the key performance indicators to be tested, such as click-through rate, conversion rate, retention rate, load time, etc.

[0221] Multivariate testing: Sometimes A / B testing is expanded to multivariate testing, testing multiple variations at the same time.

[0222] When conducting A / B testing, you need to ensure the fairness and statistical validity of the test to avoid bias. This usually requires sufficient test samples and a reasonable test cycle. In addition, you also need to ensure that the interpretation and application of the test results are reasonable and will not introduce new user experience problems.

[0223] This embodiment describes how the identity management microservice verifies the effect of the identity through grayscale release and comparative testing after updating or adding a business identity, and makes a decision on whether to fully deploy the new identity based on this.

[0224] Logo updated or added:

[0225] Through the preset configuration management tool, according to the user's configuration request, the preset identifiers in the identity control microservice are updated or new business identifiers are added.

[0226] Grayscale release:

[0227] Apply updated or new logos to a subset of users or requests rather than rolling them out across the board to assess the impact and performance of the new logo.

[0228] Collect grayscale release data:

[0229] Monitor business indicators and user feedback during the grayscale release process, such as identification execution success rate, failure rate, performance impact, etc.

[0230] Analysis of grayscale release results:

[0231] Evaluate the effectiveness of the new logo based on the data collected to determine if it meets the intended goals.

[0232] Comparative test:

[0233] The new and old logos were tested side-by-side to compare how they performed under the same conditions.

[0234] Analysis and comparison of test results:

[0235] Based on the results of the comparative test, evaluate the strengths and potential issues of the new logo relative to the old one.

[0236] Decision execution:

[0237] If the grayscale release and comparison test results are in line with expectations, a decision will be made to fully implement the new logo;

[0238] If the results are not as expected, make adjustments or roll back to the old identity.

[0239] Suppose a financial company uses an identity control microservice to validate loan applications.

[0240] Update loan approval indicator:

[0241] The financial company's business team updated the loan approval logo through the configuration management tool to take into account the new credit scoring model.

[0242] Grayscale releases new logo:

[0243] The identity control microservice applies the new identity to 10% of loan applications while keeping the old identity for 90% of applications.

[0244] Monitoring and collecting data:

[0245] The microservice monitors the execution of new logos, collecting data on approval rates, rejection rates, and processing time.

[0246] Analyze the grayscale results:

[0247] Analysis showed that approval rates for the new logos were in line with expectations, but processing times increased slightly.

[0248] Comparative test:

[0249] Conduct detailed A / B testing by applying the old and new logos side-by-side to the same set of loan applications.

[0250] Evaluate the comparative test results:

[0251] Comparative test results show that although the new logo takes a little longer to process, it can identify credit risks more accurately.

[0252] Decision making and execution:

[0253] Based on the combined results of the grayscale release and comparative testing, the financial company decided to fully deploy the new logo.

[0254] Monitor full deployment:

[0255] Once the new logo is fully deployed, continue to monitor its effectiveness to ensure there are no negative impacts.

[0256] In this way, the identity management and control microservice can ensure the quality and effectiveness of new identities and reduce the risks that new identities may bring.

[0257] Furthermore, after updating the preset identifier contained in the identifier control microservice or adding a new business identifier through the preset configuration management tool according to the configuration request, it also includes:

[0258] The identity control microservice calls the preset test case to perform automated test on the updated preset identity or the newly added business identity, and generates the test results;

[0259] If the test result is successful, the updated preset logo or the newly added business logo is released;

[0260] If the test result is a test failure, the updated preset identifier or the newly added business identifier is marked and an alarm is triggered.

[0261] It should be noted that this embodiment describes how the identity management and control microservice implements automated testing after updating or adding a business identity, and decides whether to publish a new identity or trigger an alarm based on the test results.

[0262] Preset test cases:

[0263] Define a set of test cases for business identity that are designed to verify the correctness and stability of the identity logic.

[0264] Automated test execution:

[0265] After updating or adding an identity, the identity control microservice automatically calls these preset test cases for testing.

[0266] Generate test results:

[0267] After the automated testing is completed, detailed test results are generated, including the execution status and results of the test cases.

[0268] Test result evaluation:

[0269] Evaluate the test results to determine whether the test was successful.

[0270] New logo released:

[0271] If the test results indicate that all test cases are successful, the identity control microservice will publish the updated identity or the newly added identity.

[0272] Test failure handling:

[0273] If the test fails, the identity control microservice will mark the identity and trigger an alert to notify relevant personnel.

[0274] Suppose an e-commerce platform needs to update its promotional logo for the upcoming holiday season.

[0275] Update promotion logo:

[0276] The business analyst updates the promotion logo through the configuration management tool to add the new discount condition.

[0277] Automated testing:

[0278] The badge control microservice automates test cases related to promotional badges, including checking discount calculation logic and application conditions.

[0279] Generate a test report:

[0280] After the test is completed, the microservice generates a test report showing the execution results of all test cases.

[0281] Evaluate the test results:

[0282] The test report shows that one test case failed because the new discount condition resulted in an incorrect discount calculation in a specific case.

[0283] Triggering the alarm:

[0284] As a result of the test failure, the Identity Governance microservice flags the updated promotional identity and sends an alert to the development team.

[0285] Fixes and retests:

[0286] The development team investigated the issue, found and fixed the calculation logic error, and re-executed the test.

[0287] Successfully published:

[0288] After retesting, all test cases passed. The logo control microservice released a new promotion logo.

[0289] Monitoring and Auditing:

[0290] After the new logo is launched, the system continuously monitors its performance and records all relevant actions and events.

[0291] In this way, the identity governance microservice can ensure the quality of new identities and reduce errors and risks in the production environment.

[0292] See also Figure 3 , Figure 3 Schematic diagram of the structure of the service identification configuration device based on the microservice architecture in the embodiment of the present application. Figure 3 As shown, specifically:

[0293] Processing unit 301, used for transmitting the target parameters contained in the business identifier to the identifier management microservice when the business system performs business identifier verification;

[0294] The verification unit 302 is used to verify the identification control microservice according to the business identification and target parameters, and transmit the generated verification result to the business system.

[0295] Furthermore, it also includes an identification configuration unit, which is used to:

[0296] Before executing the business identification verification, the business system receives a user's configuration request for the business identification through a user interface, and the user interface includes an identification editor;

[0297] Through the preset configuration management tool, the preset identifiers contained in the identity control microservice are updated or new business identifiers are added according to the configuration request.

[0298] Furthermore, a monitoring unit is included, which is used to:

[0299] The identity control microservice generates a monitoring report based on the verification results of the business identity;

[0300] When the monitoring report contains verification failure results that exceed the preset threshold, the identification control microservice marks the business ID and issues an alarm.

[0301] Furthermore, it also includes a permission configuration unit, which is used to:

[0302] When there are two or more business systems, the identity control microservice assigns corresponding identity access rights to each business system;

[0303] If the business system transmits the target parameters contained in the business identifier in the non-identification access permission to the identity control microservice, the identity control microservice returns a prompt of no permission to the business system.

[0304] Furthermore, it also includes an instance calling unit, which is used to:

[0305] If the preferred service instance of the identity control microservice cannot respond to the verification request for the business identity in the business system, the verification request will be forwarded to the alternative service instance until all alternative service instances fail to respond or there is a responding alternative service instance;

[0306] The identification control microservice uses the circuit breaker mode to cut off the preferred service instance or alternative service instance that fails to respond.

[0307] Furthermore, it also includes a marking test unit, which is used to:

[0308] The identity control microservice performs a grayscale release of the preset identity or the newly added business identity after the identity update, and determines whether to fully execute the preset identity or the newly added business identity after the identity update based on the grayscale release result;

[0309] The identity control microservice performs a comparison test on the preset identity or the newly added business identity after the identity update, and determines whether to fully execute the preset identity or the newly added business identity after the identity update based on the comparison test results.

[0310] Furthermore, the identification test unit is also used for:

[0311] The identity control microservice calls the preset test case to perform automated test on the updated preset identity or the newly added business identity, and generates the test results;

[0312] If the test result is successful, the updated preset logo or the newly added business logo is released;

[0313] If the test result is a test failure, the updated preset identifier or the newly added business identifier is marked and an alarm is triggered.

[0314] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Figure 4As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer program is executed by the processor, it realizes the functions or steps of the client side of an intelligent question-answering processing method based on artificial intelligence

[0315] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0316] When the business system performs business identification verification, the business system transmits the target parameters contained in the business identification to the identification control microservice;

[0317] The identity control microservice performs verification based on the business identity and target parameters, and transmits the generated verification results to the business system.

[0318] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0319] When the business system performs business identification verification, the business system transmits the target parameters contained in the business identification to the identification control microservice;

[0320] The identity control microservice performs verification based on the business identity and target parameters, and transmits the generated verification results to the business system.

[0321] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can refer to the relevant descriptions on the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0322] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0323] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0324] In the embodiments of the present application, a business identification configuration method, apparatus, equipment and medium based on a microservice architecture are provided, which separates identification control and configuration functions from the process of the business system, builds identification control on an independent microservice application, verifies various business identifications by calling the identification control microservice in the process flow logic of the business system, realizes unified identification control, further adjusts and updates identifications in real time in the identification control microservice, quickly configures identifications, and does not affect the normal flow logic of the business system, reduces the cost of identification control, and solves the technical problems of existing identification control, such as identification dispersion, difficulty in unified management and maintenance, difficulty in identification adjustment, easy impact on system stability and performance, and lack of flexibility.

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

[0326] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0327] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

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

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

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

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

[0332] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

[0333] It should be noted that if software tools or components other than those of our company appear in the embodiments of the present application, they are only used for illustrative purposes and do not represent actual use.

Claims

1. A method for configuring a business identifier based on a microservice architecture, characterized in that: include: When the business system performs business identification verification, the business system transmits the target parameters contained in the business identification to the identification management and control microservice; The identification management and control microservice performs verification according to the business identification and the target parameters, and transmits the generated verification result to the business system.

2. The method for configuring a service identifier based on a microservice architecture according to claim 1, characterized in that: Also includes: The business system receives a user's request for configuring a business identifier through a user interface before performing the business identifier verification, and the user interface includes an identifier editor; Through a preset configuration management tool, the preset identifier contained in the identifier control microservice is updated or a new business identifier is added according to the configuration request.

3. The service identification configuration method based on microservice architecture according to claim 1 is characterized in that: Also includes: The identification control microservice generates a monitoring report according to the verification result of the business identification; When there are verification failure results exceeding a preset threshold in the monitoring report, the identity management and control microservice marks the business identity and issues an alarm.

4. The method for configuring a service identifier based on a microservice architecture according to claim 1, characterized in that: Also includes: When there are two or more business systems, the identity management and control microservice allocates corresponding identity access rights to each business system; If the business system transmits the target parameter contained in the business identifier in the non-identification access permission to the identifier control microservice, the identifier control microservice returns a no-authorization prompt to the business system.

5. The method for configuring a service identifier based on a microservice architecture according to claim 1, characterized in that: When the business system performs business identification verification, the business system transmits the target parameters contained in the business identification to the identification management and control microservice, and then further includes: If the preferred service instance of the identity control microservice cannot respond to the verification request for the business identity in the business system, the verification request is forwarded to the alternative service instance until all alternative service instances fail to respond or there is a responding alternative service instance; The identification management and control microservice cuts off the preferred service instance or the alternative service instance that cannot respond using a circuit breaker mode.

6. The method for configuring a service identifier based on a microservice architecture according to claim 2, characterized in that: After the preset configuration management tool is used to update the preset identifier contained in the identifier control microservice or add a new business identifier according to the configuration request, the following further includes: The identification control microservice performs a grayscale release on the preset identification or the newly added business identification after the identification is updated, and determines whether to fully execute the preset identification or the newly added business identification after the identification is updated according to the grayscale release result; The identification control microservice performs a comparison test on the preset identification or the newly added service identification after the identification is updated, and determines whether to completely execute the preset identification or the newly added service identification after the identification is updated according to the comparison test result.

7. The method for configuring a service identifier based on a microservice architecture according to claim 6, characterized in that: After the preset configuration management tool is used to update the preset identifier contained in the identifier control microservice or add a new business identifier according to the configuration request, the following further includes: The identity management and control microservice calls a preset test case to perform an automated test case test on the preset identity or the newly added business identity after the identity is updated, and generates a test result; If the test result is a success, issuing the preset identifier or the newly added service identifier after the identifier is updated; If the test result is a test failure, the preset identifier or the newly added service identifier after the identifier is updated is marked, and an alarm is triggered.

8. A service identification configuration device based on microservice architecture, characterized in that: include: A processing unit, configured to transmit the target parameters contained in the business identifier to the identifier management and control microservice when the business system performs business identifier verification; A verification unit is used for the identification management and control microservice to verify the business identification and the target parameters, and transmit the generated verification result to the business system.

9. A service identification configuration device based on microservice architecture, characterized in that: The device comprises a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the business identification configuration method based on microservice architecture according to any one of claims 1-7 according to the instructions in the program code.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store program code, and the program code is used to execute the business identification configuration method based on microservice architecture according to any one of claims 1 to 7.

Images