Microservice creation method and device

Abstract

The invention provides a micro-service creation method and device, and relates to the technical field of data processing. The method comprises the following steps: carrying out business modeling according to business requirements associated with a financial institution to obtain a plurality of business models; generating a plurality of service capabilities according to the plurality of service models; wherein the business capability comprises a business object and a group of service functions for operating a plurality of business entities under the business object; and creating a plurality of micro-services according to the business objects in the plurality of business capabilities and the group of service functions. Therefore, the specific landing guidance of the business model on the design and development of the micro-service is taken as a principle, the design of the business capability is added between the plurality of business models and the micro-service design of the financial institution, and the complete mapping and alignment of the business models and the micro-service design are realized; the problem that the service architecture, the application architecture and the technical architecture are inconsistent in the landing implementation process is fundamentally solved, and the response speed of service innovation is increased.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to a method and device for creating a microservice. Background Art

[0002] Business modeling is a method used to design enterprise-level business architecture. It connects a company's business strategy (high-level decision-making) and technical implementation (Internet Technology (IT) design), ensuring consistency and synergy between the two. With the emergence and development of emerging technologies such as domain-driven design (DDD), distributed architectures, cloud-native technologies, and microservices, business modeling is increasingly being used in financial industry system development. These technologies improve system flexibility, scalability, and responsiveness, while also requiring system design to be more closely aligned with business needs.

[0003] In practice, business modeling is often used primarily during the business architecture planning and requirements analysis phases, specifically to define "what to do." However, when entering the technical design and development phases, many development teams revert to traditional software engineering methodologies, often paying less attention to the guiding principles provided by the business model. Business models are not fully integrated into the specific system design and development process, nor are they updated promptly with business changes (i.e., kept fresh). This phenomenon causes business models to gradually lose their value, becoming merely theoretical frameworks that fail to translate into practical product or service improvements.

[0004] In summary, because the business model was not effectively integrated into the development process, a deviation occurred between the business architecture and the final actual application architecture and technical architecture. This deviation may cause the system to fail to fully meet business needs or require additional work to adjust to the actual situation. Summary of the Invention

[0005] The present disclosure aims to solve one of the technical problems in the related art at least to a certain extent.

[0006] One aspect of the present disclosure proposes a method and apparatus for creating microservices to achieve complete mapping and alignment between business models and microservice designs, fundamentally resolving the inconsistency issues among business architecture, application architecture, and technical architecture during implementation, thereby forming a "financial institution's strategic goals-business-technology" linkage system, achieving strict alignment of each stage from business needs → business modeling → IT design → IT implementation, and improving the response speed of business innovation.

[0007] The first embodiment of the present disclosure provides a method for creating a microservice, including:

[0008] Conduct business modeling based on business requirements associated with financial institutions to obtain multiple business models;

[0009] Generating a plurality of business capabilities according to the plurality of business models; wherein the business capabilities include a business object and a set of service functions for operating a plurality of business entities under the business object;

[0010] Multiple microservices are created based on the business objects and a set of service functions in the multiple business capabilities.

[0011] A second embodiment of the present disclosure provides a device for creating a microservice, including:

[0012] A modeling module, configured to perform business modeling based on business requirements associated with financial institutions to obtain multiple business models;

[0013] A generating module, configured to generate a plurality of business capabilities according to the plurality of business models; wherein the business capabilities include business objects and a set of service functions for operating business entities under the business objects;

[0014] A creation module is used to create multiple microservices based on the business objects and a set of service functions in the multiple business capabilities.

[0015] The third embodiment of the present disclosure proposes an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the microservice creation method proposed in the first embodiment of the present disclosure is implemented.

[0016] The fourth embodiment of the present disclosure proposes a non-temporary computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the microservice creation method proposed in the first embodiment of the present disclosure.

[0017] The fifth embodiment of the present disclosure proposes a computer program product. When the instructions in the computer program product are executed by a processor, the method for creating a microservice proposed in the first embodiment of the present disclosure is executed.

[0018] The technical solutions provided by the above embodiments of the present disclosure bring at least the following beneficial effects:

[0019] Based on the principle of specific implementation guidance of the business model for the design and development of microservices, the design of business capabilities is added between the multiple business models and microservice designs of financial institutions, realizing the complete mapping and alignment of business models and microservice designs, fundamentally solving the problem of inconsistency in the implementation process of business architecture, application architecture, and technical architecture, forming a "financial institution's strategic goals-business-technology" linkage system, achieving strict alignment of each stage of business needs → business modeling → IT design → IT implementation, and improving the response speed of business innovation.

[0020] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0022] Figure 1 A flowchart of a method for creating a microservice provided in an embodiment of the present disclosure;

[0023] Figure 2 A flowchart of another method for creating a microservice provided by an embodiment of the present disclosure;

[0024] Figure 3 A flowchart of another method for creating a microservice provided by an embodiment of the present disclosure;

[0025] Figure 4 A flowchart of another method for creating a microservice provided by an embodiment of the present disclosure;

[0026] Figure 5 A schematic diagram illustrating the complete mapping and alignment principles of the business model and microservice design provided by the embodiments of the present disclosure;

[0027] Figure 6 A schematic diagram of the structure of a microservice creation device provided in an embodiment of the present disclosure;

[0028] Figure 7 It is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] The following describes in detail embodiments of the present disclosure, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0030] While current technology practices utilize business modeling for business architecture design, during the system application design and development phase, business models fail to accurately and effectively connect with actual development processes, resulting in operational methods that are not significantly different from traditional software engineering methods. This disconnect can easily lead to inconsistencies between the business architecture, application architecture, and technical architecture within the enterprise architecture, all of which together support the strategic development of financial institutions.

[0031] If there is a lack of consistency between these three layers, at least the following problems will arise:

[0032] 1. Unclear business boundaries: The natural logic of business architecture design cannot be accurately implemented, resulting in blurred business boundaries and difficulty in fully reflecting the original design intention.

[0033] 2. Limited responsiveness: In the face of business changes, the responsiveness of the application system is constrained by the technical architecture, lacking flexibility and making it difficult to quickly adapt to changes in business needs, which in turn affects the speed of business innovation.

[0034] The main causes of these problems are:

[0035] (1) Lack of specific guidance methods: In existing software project practices, there is a lack of specific guidance methods for effectively applying business modeling to system application design and development.

[0036] (2) Lack of supporting tool support: The entire development process lacks matching implementation process tools, which cannot provide full support for the transformation from business modeling to actual application and ensure that the value of the business model can be fully realized.

[0037] To address at least one of the above-mentioned problems, the present disclosure provides a method and apparatus for creating a microservice.

[0038] The following describes the method and apparatus for creating a microservice according to an embodiment of the present disclosure with reference to the accompanying drawings. Before describing the embodiment of the present disclosure in detail, for ease of understanding, the following common technical terms are first introduced:

[0039] Business Architecture: This refers to the high-level planning of a financial institution's business processes, organizational structure, information flows, and systems to achieve its strategic objectives. It provides a framework for understanding, analyzing, and optimizing how a financial institution operates and how to improve efficiency and effectiveness through information technology support. Business Architecture connects a financial institution's business strategy and IT strategy, ensuring synergy between the two.

[0040] Business Model: Business modeling abstracts a financial institution's actual business scenarios, expressing actual business needs, scenarios, and elements through models to achieve product innovation, operational optimization, and data asset accumulation. The business model, the product of business modeling, includes process models, product models, and data models, broken down from top to bottom into multiple layers (e.g., five layers) of model elements.

[0041] The relationship between business architecture and business models is as follows: 1. Guidance: Business architecture provides direction and boundaries for business models, defining which business areas need to be modeled and the strategic goals these models should support. 2. Refinement and implementation: Business models are more detailed designs of certain aspects of the business architecture, used to guide specific IT implementations. For example, in the actual operations of a financial institution, a business model might describe core business functions such as account management and transaction processing in detail. 3. Maintaining consistency: Good business architecture practices continuously update business models to reflect the latest business changes and technological advances, ensuring consistency between them and enabling the business model to effectively guide subsequent application design and technical implementation.

[0042] Product model: The product model focuses on the products of financial institutions and is the focus of business innovation in response to market changes. Taking the product model as an example, it includes five levels of model elements. The five levels of model elements contained in the product model from high to low (or top to bottom) are: product line → product group → basic product → product component → product condition.

[0043] Among them, Product Line: The highest-level classification, covering a group of related products with similar characteristics and target markets, such as "Personal Loans," "Credit Cards," and "Savings Accounts." Product Group: A further subdivision of a product line, focusing on specific types of products or services, making product management and marketing more specific and targeted, such as "Home Loans," "Auto Loans," and "Education Loans" under "Personal Loans." Base Product: A specific product instance defined within a product group, with clear functions and service content, and is a standardized product provided directly to customers, such as "Fixed-Rate Home Loans" and "Floating-Rate Home Loans" under "Home Loans." Product Component: The various components that make up a base product, which can be configured independently or used in combination to increase product flexibility and customizability, such as "Early Repayment Option" and "Insurance Supplementary Services" under "Fixed-Rate Home Loans." Product Condition: The specific parameters or rules of a product component, used to describe in detail the product's operation, restrictions, and scope of application, to ensure product consistency and compliance, such as the "Early Repayment Fee Rate" and "Minimum Early Repayment Amount" of the "Early Repayment Option."

[0044] Process model: The process model describes the business of a financial institution from the perspective of how the business process creates value. The process model includes five levels of model elements as an example. The five levels of model elements contained in the process model are as follows from high to low: business area → business stage (value stream) → activity → task → step.

[0045] Among them, Business Area: The highest-level classification, representing the broad business scope or functional area within a financial institution, such as deposits, loans, and payments; Business Stage (Value Stream): A high-level division of key business processes within a business area, representing a set of continuous activities designed to create specific value for customers or enterprises; Activity: The main work unit within a business stage, representing a set of logically related and coherent tasks that specifically achieve business goals, such as "individual customers apply for personal deposit product business"; Task: The specific component of an activity, representing the detailed operations required to complete an activity. Each task includes the task name (such as submitting account opening application materials, reviewing account opening application resources, checking customer account opening conditions, transaction authorization, opening personal savings products, etc.), the task execution role (such as customer, transaction teller, authorization teller, etc.), and the task execution method (such as offline, online, where online includes manual interaction and automatic processing); Step: The smallest execution unit of a task, representing the specific actions or instructions to complete the task, which directly affects the success of the task. Each step includes the step name and step descriptions. Taking the task of "checking customer account opening conditions, selecting account opening products, and submitting transaction authorization" as an example, the step name includes "checking customer information" and the step description includes "1. Check whether the customer is a blacklisted customer. If so, the transaction is blocked; 2. Check the customer's online identity information. If the verification fails, the transaction is blocked." For another example, the step name includes "checking customer account information" and the step description includes "1. Confirm the classification identifier and voucher type of the account to be opened: the classification identifier is Class I account, Class II account, and Class III account. When it is a personal current passbook, the classification identifier defaults to Class I account and cannot be modified; 2. Check whether there is an unclosed Class I account under the customer." For another example, the step name includes "select saleable products and distributed vouchers" and the step description includes "1. Select saleable products and distributed media; 2. Determine the voucher type and voucher number." For another example, the step name includes "determine the account opening interest rate" and the step description includes "according to the benchmark interest rate and basis points (Basis Points)". For another example, the step name includes "determine the medium withdrawal method and password", and the step description includes "determine the withdrawal method and password: when the deposit type is current and the voucher type is passbook, the withdrawal method can be selected: voucher / passbook, document, and password". For another example, the step name includes "design transaction permissions", and the step description includes "set the non-counter daily / annual cumulative limit and cumulative number of transactions".

[0046] Data model: The data model describes how the business process changes the business status by operating data from the perspective of business data. The data model includes five levels of model elements as an example. The five levels of model elements contained in the data model are as follows from high to low: subject domain → sub-subject domain → business object → business entity → entity attribute.

[0047] Among them, the subject area is the top-level data classification, representing the broad business areas or data areas within a financial institution, such as "resource items" and "products". Sub-subject areas are more detailed divisions of the subject area, focusing on specific business aspects or functional modules, such as "tail box" and "business library" under "resource items". Business objects are logical entities defined within sub-subject areas, representing key concepts or participants in the business process, such as "business middle office (tail box management)", "business middle office (interest calculation center)", "business middle office (account center)", and "deposit business (personal current account settlement execution transaction)". Business entities are specific instances of business objects with independent identities, and each business entity has corresponding operation types (such as query, create, update, etc.). Business entities include but are not limited to "tail box information", "interest rate tiering information", "balance account information", and "personal current account settlement account opening and closing transaction details". Entity attributes describe the specific characteristics and parameters of business entities.

[0048] Business capabilities: By integrating the three core business models of process model, product model, and data model, we cluster and form highly cohesive, loosely coupled, and reusable business capabilities. Business capabilities can also be divided into five levels from large to small: capability domain → capability group → business capability → service function → business rules (standardization). Each level has clear responsibilities and roles to ensure that the business strategy can be implemented layer by layer from top to bottom.

[0049] Among them, business capabilities include business middle-office capabilities (i.e., public capabilities (business capabilities common to multiple business areas)) and single business area capabilities. For example, business middle-office capabilities include customer center (query, creation, and update of basic customer information in different business areas such as deposits, loans, and payments), contract center (query, creation, and update of contract information in different business areas), interest calculation center (query, creation, and update of interest rate information in different business areas), etc. Single business capabilities include: basic product capabilities for personal current settlement deposits (such as executing transactions such as opening personal current settlement accounts), deposit transaction control checks (checking deposit transaction permission controls, etc.), etc.

[0050] Among them, capability domain: the top-level business classification, covering all major business areas of financial institutions, such as deposits, loans, payments, etc.; capability group: the subdivision area under the capability domain, further refining the business scope; business capability: the capability unit that specifically implements a specific business function; service function: the specific operations and services that constitute business capabilities. For example, service functions may include "querying basic customer information" under the "customer center" and "querying contract information" under the "contract center"; business rules (standardization): the specific rules and standards that guide the execution of service functions to ensure consistency.

[0051] In a broad sense, business capabilities refer to the high-level capabilities that financial institutions must possess and enhance to achieve their business strategies. They represent the core competencies required to achieve their strategic goals, encompassing a broad range of business needs and high-level business logic. Unlike broad business capabilities, the business capabilities discussed in this disclosure focus more on IT design and are a closed set of business objects and the logical processing of those objects. Specifically, a business capability encompasses a business object and a set of service functions that operate on multiple business entities within that business object. Business capabilities are key to the convergence of business and technology, serving as a bridge between the realization of business strategic capabilities and application development.

[0052] Microservices: In a distributed architecture, microservices are a group of smaller services developed from a single application (app) in a centralized distributed architecture. The application's user interface (UI) and application programming interface (API) are separated into two independently running components, with microservices consisting solely of the API. Each microservice runs in its own process, communicating with each other using lightweight mechanisms. Microservices are built around business capabilities and can be independently deployed through fully automated deployment mechanisms.

[0053] Figure 1 A flowchart of a method for creating a microservice provided in an embodiment of the present disclosure.

[0054] The embodiment of the present disclosure takes the microservice creation method configured in a microservice creation device as an example. The microservice creation device can be applied to any electronic device so that the electronic device can perform the microservice creation function.

[0055] Among them, the electronic device can be any device with computing capabilities, such as a personal computer, mobile terminal, server, etc. The mobile terminal can be, for example, a mobile phone, tablet computer, personal digital assistant, wearable device, etc., which are hardware devices with various operating systems, touch screens and / or display screens.

[0056] like Figure 1 As shown, the method for creating a microservice includes the following steps S101 to S103:

[0057] Step S101 : performing business modeling according to business requirements associated with financial institutions to obtain multiple business models.

[0058] Business requirements refer to the specific conditions, functions and restrictions that need to be met in order to achieve the business strategy and operational efficiency of financial institutions.

[0059] For example, in order to improve the richness, completeness and accuracy of business modeling, business needs can be described in a structured manner from different perspectives and dimensions such as product rules, business collaboration, and business information. The business needs can reflect the demand descriptions of various stakeholders within the financial institution for new products, services or process improvements.

[0060] The business model includes, but is not limited to, product models, process models, and data models. The process model connects the product model and the data model in series. That is, the product-related business rules in the model elements (e.g., steps) at the final level of the process model are subject to the instantiation constraints of the product model, and the model elements (e.g., steps) at the final level of the process model operate on the business entities in the data model.

[0061] For example, taking a bank as an example of a financial institution, based on the bank's business needs, business modeling can be carried out on the basis of the business modeling method framework in the "Guidelines for Banking Business Modeling" (draft for approval) in financial standard technology to establish multiple business models.

[0062] Step S102 : generating a plurality of business capabilities according to a plurality of business models; wherein the business capabilities include a business object and a set of service functions of a business entity operating under the business object.

[0063] Each business capability includes a business object and a set of service functions for operating multiple business entities under the business object.

[0064] For example, multiple service functions can be generated or designed based on model elements at multiple levels within multiple business models. Then, based on the clustering principle, these service functions can be clustered according to their business relevance to derive multiple business capabilities. Specifically, a set of closely related service functions can be identified based on business relevance, and consensus can be achieved between all business entities operated by these closely related service functions and all service functions that operate on the business objects to which these business entities belong, thereby forming highly cohesive, loosely coupled, and reusable business capabilities.

[0065] Step S103: Create multiple microservices based on the business objects in the multiple business capabilities and a set of service functions.

[0066] There is a one-to-one correspondence between business capabilities and microservices, and microservices can be used to provide business functions for financial institutions.

[0067] In the embodiment of the present disclosure, for any one of the multiple business capabilities, a microservice corresponding to the business capability can be created based on the business objects and a set of service functions in the business capability.

[0068] The microservice creation method of the disclosed embodiment is based on the principle of specific implementation guidance of the business model for the design and development of microservices. It adds the design of business capabilities between the multiple business models and microservice designs of financial institutions, realizes the complete mapping and alignment of business models and microservice designs, and fundamentally solves the problem of inconsistency between business architecture, application architecture, and technical architecture during the implementation process, forming a "financial institution's strategic goals-business-technology" linkage system, achieving strict alignment of each stage of business needs → business modeling → IT design → IT implementation, and improving the response speed of business innovation.

[0069] It should be noted that in the technical solutions disclosed herein, the collection, storage, use, processing, transmission, provision and disclosure of user personal information are all carried out with the user's consent, and are in compliance with relevant laws and regulations and do not violate public order and good morals.

[0070] In order to clearly illustrate how multiple business capabilities are generated according to multiple business models in the above embodiments, the present disclosure also proposes a method for creating microservices.

[0071] Figure 2 A flowchart of another method for creating a microservice provided in an embodiment of the present disclosure.

[0072] It should be noted that the method for creating the microservice can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in the embodiment, or it can be executed in combination with any technical solution in the related technology, and the embodiments of the present disclosure are not limited to this.

[0073] like Figure 2 As shown, the method for creating a microservice includes the following steps S201 to S205:

[0074] Step S201 , business modeling is performed according to business requirements associated with the financial institution to obtain multiple business models; wherein the business model includes model elements at multiple levels, including product models, process models and data models.

[0075] Among them, the process model connects the product model and the data model in series, that is, the product-related business rules involved in the model elements (such as steps) at the last level in the process model are subject to the instantiation constraints of the product model, and the model elements (such as steps) at the last level in the process model operate the business entities in the data model.

[0076] The product model, process model and data model each contain N levels of model elements, where N is a positive integer. For example, N may be 5.

[0077] It should be noted that, for the explanation of step S201 , reference can be made to the relevant description in any embodiment of the present disclosure, and no further details are given here.

[0078] Step S202 : determining the execution role and execution mode of each model element at the end level in the process model, and determining the business object to which a business entity in the data model operated by each model element at the end level belongs.

[0079] The execution role of each model element at the final level in the process model can use the name of the business object to which the business entity operated by the model element at the final level belongs. For example, a process model includes five levels of model elements: business domain → business stage (value stream) → activity → task → step. The final model element can be a step, and the execution role can use the name of the business object operated by the step.

[0080] Among them, business objects include a group of closely related business entities in the data model.

[0081] The execution mode of each model element at the end level in the process model includes but is not limited to: manual interaction, automatic processing, etc.

[0082] Each model element at the end level in the process model operates on a business entity in the data model.

[0083] In an embodiment of the present disclosure, multiple business models can be analyzed to determine the business object to which a business entity in a data model operated by each end-level model element (such as a step) in the process model belongs, and to determine the execution role and execution method of each end-level model element (such as a step) in the process model.

[0084] Step S203 : generating a plurality of service functions according to the execution roles, execution modes and operation business objects of the model elements at each end level.

[0085] In the disclosed embodiments, multiple service functions can be generated based on the execution roles, execution methods, and business objects of the model elements at the final level in the process model. For example, model elements (e.g., steps) at the final level that are executed consecutively with the same execution role and execution method and that operate on the same business object can be designed as a single service function.

[0086] As an example, the model elements at each end level in the process model can be divided according to the execution roles, execution methods and business objects of each operation of the model elements at each end level to obtain multiple groups, wherein the execution roles, execution methods and business objects of each model element in the same group are the same, and each model element in the same group is a continuously executed model element. Therefore, in the present disclosure, a service function can be designed or generated based on each model element in the same group, wherein the group and the service function are in a one-to-one correspondence.

[0087] The process model includes five levels of model elements, namely business domain → business stage (value stream) → activity → task → step, for example. The model element at the last level can be a step. In this disclosure, based on the principle of "each step operates a business entity, and the operation type of each business entity is determined (such as addition, deletion, and modification)", the execution role, execution method (manual interaction or automatic processing) and business object of the corresponding step are further clarified, and the steps with the same execution role, execution method, and continuous execution of the same business object are designed as a service function.

[0088] Step S204: clustering the multiple service functions according to the business relevance between the multiple service functions to obtain multiple business capabilities.

[0089] Each business capability includes a business object in the data model and a set of service functions for operating business entities under the business object.

[0090] In the disclosed embodiments, multiple service functions can be clustered based on the clustering principle and the business relevance between them to obtain multiple business capabilities. Specifically, a group of closely related service functions is identified based on business relevance, and consistency is achieved between all business entities operated by these closely related service functions and all service functions that operate on the business objects to which these business entities belong, thereby forming highly cohesive, loosely coupled, and reusable business capabilities.

[0091] Step S205: Create multiple microservices based on the business objects in the multiple business capabilities and a set of service functions.

[0092] It should be noted that, for the explanation of step S205 , reference can be made to the relevant description in any embodiment of the present disclosure, and no further details are given here.

[0093] The microservice creation method of the embodiment of the present disclosure builds highly cohesive, loosely coupled, and reusable business capabilities through standardization and clustering in two stages (the first stage is to design service functions, and the second stage is to cluster service functions to obtain business capabilities). It has at least the following advantages: through modular design, each business capability is executed for a specific business object, and a single business capability can be independently developed, tested, and deployed, which improves development efficiency and iteration speed, reduces the mutual dependence between different modules, and reduces the mutual influence between modules; highly cohesive business capabilities can be reused in different business scenarios, reducing the writing of redundant code and improving the overall quality of the system.

[0094] In order to clearly illustrate how to create multiple microservices based on business objects in multiple business capabilities and a set of service functions in any embodiment of the present disclosure, the present disclosure also proposes a method for creating microservices.

[0095] Figure 3 A flowchart of another method for creating a microservice provided in an embodiment of the present disclosure.

[0096] It should be noted that the method for creating the microservice can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in the embodiment, or it can be executed in combination with any technical solution in the related technology, and the embodiments of the present disclosure are not limited to this.

[0097] like Figure 3 As shown, the method for creating a microservice includes the following steps S301 to S305:

[0098] Step S301 : performing business modeling according to business requirements associated with financial institutions to obtain multiple business models.

[0099] Step S302 : generating a plurality of business capabilities according to a plurality of business models; wherein the business capabilities include a business object and a set of service functions of a business entity operating under the business object.

[0100] It should be noted that, for the explanation of steps S301 to S302 , reference can be made to the relevant description in any embodiment of the present disclosure, and no further details are given here.

[0101] Step S303 : for any business capability among the multiple business capabilities, based on a set of service functions included in any business capability, create multiple APIs for implementing the set of service functions; wherein the service functions and the APIs are in a one-to-one correspondence.

[0102] In an embodiment of the present disclosure, for any one of the multiple business capabilities, an API for implementing each service function in the set of service functions can be created based on a set of service functions included in the business capability, wherein the service function and the API are in a one-to-one correspondence, that is, one API is used to implement one service function.

[0103] Step S304: Generate a domain model based on the business objects included in any business capability.

[0104] The domain model is used to indicate the data processing scope of the microservice. The domain model is a data model formed based on business objects, including a root entity, multiple supporting entities, and value objects.

[0105] In the embodiment of the present disclosure, for any one of the multiple business capabilities, a domain model corresponding to the business object can be generated according to the business object included in the business capability.

[0106] As an example, first, multiple sub-fields can be obtained by dividing the business fields involved in multiple business models, where the sub-fields include but are not limited to: deposits, loans, payments and other fields. Then, the sub-field to which the business capability belongs can be identified from the multiple sub-fields, which is recorded as the target sub-field in this disclosure. Then, a domain model corresponding to the target sub-field can be generated based on the business objects and target sub-fields contained in the business capability.

[0107] Step S305: Create a microservice corresponding to any business capability based on multiple APIs and domain models.

[0108] In the embodiment of the present disclosure, microservices corresponding to the business capabilities can be created based on the multiple APIs and domain models, that is, each microservice includes the multiple APIs and domain models. There is a one-to-one correspondence between business capabilities and microservices.

[0109] In any embodiment of the present disclosure, after multiple microservices are created, business activities in the financial institution can be executed by calling APIs in the multiple microservices. For example, the following steps A to D can be used to execute business activities in the financial institution:

[0110] Step A: Determine the service function involved in the business activity to be executed in the financial institution (such as individual customers opening personal deposit product business, etc.) from multiple service functions, which is recorded as the target service function in this disclosure.

[0111] Step B: Determine target APIs corresponding to multiple target service functions from the APIs in multiple microservices.

[0112] Among them, the target API is an API used to implement the target service function, and there is a one-to-one correspondence between the target API and the target service function.

[0113] Step C: Determine the calling order of multiple target APIs according to the arrangement order of multiple target service functions.

[0114] Exemplarily, the arrangement order of the multiple target service functions may be determined according to the dependency relationships among the multiple target service functions, and the calling order of the target APIs corresponding to the multiple target service functions may be determined according to the arrangement order of the multiple target service functions.

[0115] Step D: Based on the calling order, call the target APIs in multiple microservices in sequence to perform business activities.

[0116] This ensures that business activities in financial institutions can be carried out in an orderly and accurate manner, ensures the consistency and accuracy of business logic, and improves the reliability and stability of the system.

[0117] In the microservice creation method of the embodiment of the present invention, the microservice design adopts the domain-driven design (DDD) method, and the business modeling is seamlessly connected with the domain-driven design method, dividing the business domain into multiple sub-domains, and directly mapping the business capabilities to the corresponding sub-domains. The service functions included in the business capabilities correspond to the APIs in the microservices, and the business objects included in the business capabilities correspond to the domain models of the corresponding sub-domains in the microservices. That is, the design of the domain model is consistent with the business objects of the data model, which can improve the consistency of business and technology, enhance the modularity of the system (that is, each microservice focuses on a specific sub-domain and has a clear functional boundary, which reduces the dependency between different modules and improves the modularity of the system) and maintainability.

[0118] In order to clearly illustrate any of the above embodiments of the present disclosure, the present disclosure also provides a method for creating a microservice.

[0119] Figure 4 A flowchart of another method for creating a microservice provided in an embodiment of the present disclosure.

[0120] It should be noted that the method for creating the microservice can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in the embodiment, or it can be executed in combination with any technical solution in the related technology, and the embodiments of the present disclosure are not limited to this.

[0121] like Figure 4As shown, the method for creating a microservice includes the following steps S401 to S404:

[0122] Step S401: Acquire business requirements, business scenarios, and business elements associated with the financial institution.

[0123] Among them, business needs can be obtained from different perspectives and multi-dimensional structured descriptions such as financial institutions' product rules, business collaboration, and business information.

[0124] Among them, business scenarios include but are not limited to loan approval processes, customer account opening services, payment transaction processing, etc.

[0125] Among them, business elements include key entities involved in business scenarios, such as customers, accounts, transaction records, financial products, etc., as well as the relationships and interaction rules between key entities.

[0126] Step S402 : performing business modeling according to business requirements, business scenarios, and business elements to obtain multiple business models.

[0127] The business model includes, but is not limited to, product models, process models, and data models. The process model connects the product model and the data model in series. That is, the product-related business rules in the model elements (e.g., steps) at the final level of the process model are subject to the instantiation constraints of the product model, and the model elements (e.g., steps) at the final level of the process model operate on the business entities in the data model.

[0128] In the disclosed embodiments, the actual scenarios of financial institutions can be abstracted through business modeling, and the actual business needs, business scenarios, and business elements can be expressed in the form of models to obtain multiple business models to achieve product innovation, operation optimization, and data asset accumulation.

[0129] For example, taking a bank as an example of a financial institution, business modeling can be carried out based on the bank's business needs, business scenarios, and business elements, and on the basis of the business modeling method framework in the "Guidelines for Banking Business Modeling" (draft for approval) in financial standard technology, to establish multiple business models.

[0130] Step S403: Generate multiple business capabilities based on multiple business models; wherein the business capabilities include a business object and a group of service functions of multiple business entities under the operation business object.

[0131] Step S404: Create multiple microservices based on the business objects in the multiple business capabilities and a set of service functions.

[0132] It should be noted that, for the explanation of steps S403 to S404, reference can be made to the relevant description in any embodiment of the present disclosure, and no further details are given here.

[0133] In any embodiment of the present disclosure, after multiple microservices are created, a mapping relationship between the microservices, business capabilities, and model elements in the business model may be established. Exemplarily, the mapping relationship may be established by following steps E to G:

[0134] Step E: For any business capability among the multiple business functions, a model element associated with the business capability can be determined from the model elements in the multiple business models, wherein the business capability includes a business object and a set of service functions for operating multiple business entities under the business object.

[0135] Exemplarily, the model elements associated with the business capability may include activities, tasks, and steps in a process model, and business objects, business entities, and entity attributes in a data model.

[0136] Step F: Determine the microservice corresponding to the business capability from among the microservices.

[0137] Step G: Establish a mapping relationship between the above-mentioned associated model elements, business capabilities and corresponding microservices.

[0138] Therefore, in this disclosure, when business requirements change, resulting in updates to one or more model elements in multiple business models, the business capabilities and microservices that are mapped to the updated model elements can be determined based on the aforementioned mapping relationships. Based on these updated model elements, these mapped business capabilities and microservices can then be synchronously or dynamically updated. This allows for rapid adaptation to changing business requirements, improving the responsiveness of business innovation and meeting actual business needs.

[0139] The microservice creation method of the embodiment of the present disclosure integrates business scenarios and business elements associated with financial institutions to perform business modeling, which can improve modeling accuracy.

[0140] In any embodiment of the present disclosure, taking a financial institution as an example, a business modeling implementation method that aligns the business model with the microservice design can be developed based on the business modeling method framework in the "Guidelines for Banking Business Modeling" (draft for approval) and through the practice of building distributed core business systems in the banking industry. Based on the principle of providing specific implementation guidance for microservice design and development using the business model, the inconsistency problem among the business architecture, application architecture, and technical architecture during implementation is fundamentally resolved, forming a "strategy-business-technology" linkage system to achieve strict alignment of each stage from business needs → business modeling → IT design → IT implementation, thereby improving the response speed of business innovation.

[0141] As an example, the principle of adding business capabilities between business models and microservice designs to achieve complete mapping and alignment between business models and microservice designs can be as follows: Figure 5 As shown, it mainly includes the following steps:

[0142] Step one: Build a business model.

[0143] Based on the business modeling method framework in the "Guidelines for Banking Business Modeling" (draft for approval) in financial standard technology, business modeling is carried out to establish product models, process models, and data models.

[0144] Step 2: Clustering business capabilities.

[0145] This is done in two phases. The first phase: Based on the standardized tasks or steps of the process model, and adhering to the principle of "each step operates on a business entity and determines the type of operation for each business entity (such as query, create, update)," further clarifies the execution role, execution method, and business object of the corresponding step. After supplementing the design perspective steps, steps that are executed consecutively under the same execution role, execution method, and business object are designed as a service function. The second phase: Based on the clustering principle and the relevance of the business, a group of closely related service functions is identified. Agreement is reached between all business entities operated by these service functions and all service functions that operate on the business objects to which this business entity belongs, thus forming a highly cohesive, loosely coupled, and reusable business capability.

[0146] Step 3: Design microservices.

[0147] In a cloud-native application architecture, microservices are built around business capabilities, with business modeling determining the boundaries of microservices. Microservice design utilizes domain-driven design (DDD) methodologies, seamlessly integrating business modeling and DDD approaches. The business domain is divided into multiple subdomains, with business capabilities directly mapped to these subdomains. Furthermore, the domain model design aligns with the business objects in the data model. Business modeling makes DDD practical within a cloud-native application architecture, making it a native microservice design approach that integrates business and technology. Business capabilities are implemented by microservices. The service functions within these capabilities correspond to the APIs within the microservices, and the business objects within these capabilities correspond to the domain models within the microservices. Multiple service functions across business capabilities are orchestrated and combined into a transaction order, supporting a process segment (sub-process) within an activity, which is then invoked by the transaction engine.

[0148] Ultimately, through clustering, business capabilities are aligned and mapped with microservice designs and business models, achieving alignment and ensuring consistency between business modeling and IT design. For example, the mapping relationship between business capabilities, business models, and microservice designs can be shown in Table 1.

[0149] Table 1 Mapping relationship between business capabilities, business models, and microservice designs

[0150]

[0151]

[0152] In summary, the microservice creation method provided in this disclosure includes at least the following features:

[0153] 1. Optimize the methodology of the "Banking Business Modeling Guide" and add business capability design between business models and microservices design to achieve complete alignment between business models and application architecture. This will enable continuous preservation of business models, promote the integration of business and technology, form a "strategy-business-technology" linkage system, improve system development quality and efficiency, and quickly respond to business needs.

[0154] 2. Build a bank-wide perspective, identify and enrich enterprise-level capabilities, form business models, business capabilities and matching microservices in the banking field, and be able to continuously maintain the business model, promote the integration of business and technology, and promote the implementation of enterprise digital transformation.

[0155] In order to implement the above embodiments, the present disclosure also provides a device for creating a microservice.

[0156] Figure 6 A schematic diagram of the structure of a microservice creation device provided in an embodiment of the present disclosure.

[0157] like Figure 6 As shown, the microservice creation device 600 includes: a modeling module 610, a generation module 620 and a creation module 630.

[0158] The modeling module 610 is used to perform business modeling based on business requirements associated with financial institutions to obtain multiple business models;

[0159] A generating module 620 is configured to generate a plurality of business capabilities based on a plurality of business models; wherein the business capabilities include a business object and a set of service functions of the business entities under the business object;

[0160] The creation module 630 is used to create multiple microservices based on the business objects in the multiple business capabilities and a set of service functions.

[0161] In a possible implementation of the embodiment of the present disclosure, the business model includes model elements of multiple levels, and the business model includes a product model, a process model and a data model, wherein the process model concatenates the product model and the data model; the generation module 620 is specifically used to: determine the execution role and execution mode of the model elements of each last level in the process model, and the business object to which a business entity in the data model operated by the model elements of each last level belongs; generate multiple service functions based on the execution role, execution mode and business object operated by the model elements of each last level; cluster the multiple service functions based on the business correlation between the multiple service functions to obtain multiple business capabilities; wherein each business capability includes a business object in the data model and a set of service functions that operate multiple business entities under one business object.

[0162] In a possible implementation of the embodiment of the present disclosure, the generation module 620 is specifically used to: divide the model elements of each last level according to the execution role, execution method and business object of the operation of the model elements of each last level to obtain multiple groups; wherein the execution role, execution method and business object of each model element in the same group are the same, and each model element in the same group is a continuously executed model element; and generate a service function based on each model element in the same group.

[0163] In a possible implementation of the embodiment of the present disclosure, a creation module 630 is specifically used to: for any business capability among multiple business capabilities, based on a set of service functions included in any business capability, create multiple application program interfaces APIs for implementing a set of service functions; wherein the service functions and APIs are in a one-to-one correspondence; generate a domain model based on the business objects included in any business capability; and create a microservice corresponding to any business capability based on multiple APIs and domain models.

[0164] In a possible implementation of the embodiment of the present disclosure, a module 630 is created, which is specifically used to: obtain multiple sub-domains obtained by dividing the business domains involved in multiple business models; identify the target sub-domain to which any business capability belongs from the multiple sub-domains; and generate a domain model corresponding to the target sub-domain based on the business objects and target sub-domains contained in any business capability.

[0165] In a possible implementation of the embodiment of the present disclosure, the microservice creation device 600 further includes:

[0166] The calling module is used to determine multiple target service functions involved in the business activities to be executed in the financial institution; determine the target APIs corresponding to the multiple target service functions from the APIs in the multiple microservices; determine the calling order of the multiple target APIs according to the arrangement order of the multiple target service functions; and call the target APIs in the multiple microservices in sequence based on the calling order to execute the business activities.

[0167] In a possible implementation of the embodiment of the present disclosure, the microservice creation device 600 further includes:

[0168] Establish a module for determining, from model elements in multiple business models, model elements associated with any business capability; wherein any business capability includes a business object and a set of service functions for multiple business entities operating under the business object; determine, from each microservice, a microservice corresponding to any business capability; and establish a mapping relationship between the associated model elements, any business capability, and the corresponding microservice.

[0169] In a possible implementation of the embodiments of the present disclosure, the mapping relationship is used to: when any model element in multiple business models is updated, determine the business capabilities and microservices that have a mapping relationship with any updated model element; and based on any updated model element, synchronously update the business capabilities and microservices that have a mapping relationship.

[0170] In a possible implementation of the embodiment of the present disclosure, the modeling module 610 is specifically used to: obtain business requirements, business scenarios and business elements associated with financial institutions; perform business modeling based on the business requirements, business scenarios and business elements to obtain multiple business models.

[0171] It should be noted that the microservice creation device provided in the embodiment of the present disclosure can achieve the above Figures 1 to 5 All the method steps implemented in the method embodiment can achieve the same technical effects, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0172] In order to implement the above embodiments, the present disclosure also proposes an electronic device, wherein the electronic device can be any device with computing capabilities, and the electronic device includes: a memory, a processor, and a computer program stored in the memory and runnable on the processor. When the processor executes the program, it implements the microservice creation method proposed in any of the aforementioned embodiments of the present disclosure.

[0173] As an example, Figure 7 is a structural diagram of an electronic device 700 shown in an exemplary embodiment of the present disclosure, such as Figure 7 As shown, the electronic device 700 may further include:

[0174] The memory 710 and the processor 720, and the bus 730 connecting different components (including the memory 710 and the processor 720), the memory 710 stores a computer program, and when the processor 720 executes the program, the method for creating a microservice described in the embodiment of the present disclosure is implemented.

[0175] Bus 730 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0176] The electronic device 700 typically includes a variety of electronic device-readable media, which can be any available media that can be accessed by the electronic device 700, including volatile and non-volatile media, removable and non-removable media.

[0177] The memory 710 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 740 and / or cache memory 750. The server 700 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 760 may be used to read and write non-removable, non-volatile magnetic media ( Figure 7 Not shown, often called a "hard drive"). Although Figure 7 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 730 via one or more data medium interfaces. Memory 710 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of various embodiments of the present disclosure.

[0178] A program / utility 780 having a set (at least one) of program modules 770 may be stored, for example, in memory 710. Such program modules 770 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may include an implementation of a network environment. Program modules 770 generally implement the functions and / or methods of the embodiments described herein.

[0179] The electronic device 700 can also communicate with one or more external devices 790 (e.g., a keyboard, a pointing device, a display 791, etc.), one or more devices that enable a user to interact with the electronic device 700, and / or any device that enables the electronic device 700 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication can occur via an input / output (I / O) interface 792. Furthermore, the electronic device 700 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network such as the Internet) via a network adapter 793. As shown, the network adapter 793 communicates with other modules of the electronic device 700 via a bus 730. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 700, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0180] The processor 720 executes various functional applications and data processing by running programs stored in the memory 710 .

[0181] It should be noted that the implementation process and technical principles of the electronic device of this embodiment can be found in the aforementioned explanation of the method for creating microservices in the embodiment of the present disclosure, and will not be repeated here.

[0182] In order to implement the above embodiments, the present disclosure further proposes a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the microservice creation method proposed in any of the above embodiments of the present disclosure.

[0183] In order to implement the above embodiments, the present disclosure further proposes a computer program product. When the instructions in the computer program product are executed by a processor, the method for creating a microservice proposed in any of the above embodiments of the present disclosure is executed.

[0184] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and features of different embodiments or examples, unless they are mutually inconsistent.

[0185] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. Throughout the present disclosure, "plurality" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0186] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present disclosure includes additional implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.

[0187] The logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and a portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing it in another suitable manner if necessary, and then storing it in a computer memory.

[0188] It should be understood that various parts of the present disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used to implement: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0189] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0190] In addition, the functional units in the various embodiments of the present disclosure may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

[0191] The storage medium mentioned above may be a read-only memory, a magnetic disk, or an optical disk, etc. Although the embodiments of the present disclosure have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. A person of ordinary skill in the art may make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A method for creating a microservice, characterized in that: include: Conduct business modeling based on business requirements associated with financial institutions to obtain multiple business models; Generating a plurality of business capabilities according to the plurality of business models; wherein the business capabilities include a business object and a set of service functions for operating a plurality of business entities under the business object; Multiple microservices are created based on the business objects and a set of service functions in the multiple business capabilities.

2. The method according to claim 1, characterized in that The business model includes model elements at multiple levels, including a product model, a process model, and a data model, wherein the process model is a serial connection between the product model and the data model; Generating a plurality of business capabilities according to the plurality of business models includes: Determining the execution role and execution mode of each model element at the last level in the process model, and the business object to which a business entity in the data model operated by each model element at the last level belongs; generating a plurality of service functions according to the execution roles, execution modes and business objects of the operations of the model elements at the end levels; Clustering the multiple service functions according to the business relevance between the multiple service functions to obtain the multiple business capabilities; Each of the business capabilities includes a business object in the data model and a set of service functions for operating multiple business entities under the business object.

3. The method according to claim 2, characterized in that The generating of multiple service functions according to the execution role, execution mode and operation business object of each model element at the end layer includes: The model elements at each of the last layers are divided into a plurality of groups according to the execution roles, execution modes, and business objects of the operations of the model elements at each of the last layers; wherein the execution roles, execution modes, and business objects of the operations of the model elements in the same group are the same, and the model elements in the same group are model elements that are executed continuously; One service function is generated according to each model element in the same group.

4. The method according to claim 1, wherein The step of creating multiple microservices based on the business objects and a set of service functions in the multiple business capabilities includes: For any one of the multiple business capabilities, based on a set of service functions included in the any one of the multiple business capabilities, create multiple application programming interfaces (APIs) for implementing the set of service functions; wherein the service functions and the APIs are in a one-to-one correspondence; Generate a domain model based on the business objects included in any of the business capabilities; A microservice corresponding to any one of the business capabilities is created based on the multiple APIs and the domain model.

5. The method according to claim 4, characterized in that Generating a domain model according to the business objects included in any one of the business capabilities includes: Acquire multiple sub-fields obtained by dividing the business fields involved in the multiple business models; Identifying a target sub-field to which any one of the business capabilities belongs from the multiple sub-fields; A domain model corresponding to the target sub-domain is generated according to the business objects included in any one of the business capabilities and the target sub-domain.

6. The method according to claim 4, characterized in that The method further comprises: determining a plurality of target service functions involved in a business activity to be performed in the financial institution; Determine, from the APIs in the multiple microservices, target APIs corresponding to the multiple target service functions; Determining a calling order of the plurality of target APIs according to an arrangement order of the plurality of target service functions; Based on the calling order, the target APIs in the multiple microservices are called in sequence to execute the business activity.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Determining, from the model elements in the plurality of business models, a model element associated with any business capability; wherein the any business capability includes a business object and a set of service functions for operating a plurality of business entities under the business object; Determine a microservice corresponding to any one of the business capabilities from among the microservices; A mapping relationship is established between the associated model element, any business capability, and the corresponding microservice.

8. The method according to claim 7, characterized in that The mapping relationship is used for: When any model element in the multiple business models is updated, determining business capabilities and microservices that have a mapping relationship with any updated model element; Based on any updated model element, the business capabilities and microservices having the mapping relationship are synchronously updated.

9. The method according to any one of claims 1 to 6, characterized in that The business modeling is performed based on the business needs associated with the financial institution to obtain multiple business models, including: Obtaining business requirements, business scenarios, and business elements associated with the financial institution; Business modeling is performed according to the business requirements, the business scenarios, and the business elements to obtain the multiple business models.

10. A device for creating a microservice, characterized in that: include: A modeling module, configured to perform business modeling based on business requirements associated with financial institutions to obtain multiple business models; A generating module, configured to generate a plurality of business capabilities according to the plurality of business models; wherein the business capabilities include business objects and a set of service functions for operating business entities under the business objects; A creation module is used to create multiple microservices based on the business objects and a set of service functions in the multiple business capabilities.

Images