CN110825359A - Transaction scheduling engine and construction and scheduling method, system, device and medium thereof - Google Patents
Transaction scheduling engine and construction and scheduling method, system, device and medium thereof Download PDFInfo
- Publication number
- CN110825359A CN110825359A CN202010033050.5A CN202010033050A CN110825359A CN 110825359 A CN110825359 A CN 110825359A CN 202010033050 A CN202010033050 A CN 202010033050A CN 110825359 A CN110825359 A CN 110825359A
- Authority
- CN
- China
- Prior art keywords
- service
- component
- transaction
- outlet
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a transaction scheduling engine, a construction method, a scheduling method, a system, a device and a medium thereof. The method comprises the following steps: developing a program corresponding to the components, wherein each component is provided with a component inlet and a component outlet, and result data executed by each component is stored in a component outlet data space; one or more components are sequentially combined into a service, the service is completed when the components are sequentially executed, a service inlet and a service outlet are configured, result data executed by each service is stored in a service outlet data space, and the service outlet is provided with a mapping relation with each component outlet of the component outlet data space; a plurality of services are combined into a transaction, a transaction entry and a transaction exit are configured, each component entry obtains component input data from a service entry or component exit data space, and each service entry obtains service input data from a transaction entry or service exit data space. The invention has the advantages of modular dynamic configuration, multi-dimensional transaction, service measurement and uniform programming interface, and is suitable for rapid change and iteration of business requirements.
Description
Technical Field
The invention relates to the field of transaction operation processing bottom layer scheduling on a financial business platform, in particular to a dynamic configuration technical method for splitting transaction products by a financial business model, and specifically relates to a transaction scheduling engine, a construction and scheduling method, a system, a device and a medium thereof.
Background
Traditional financial outlets such as banks and stock offices mainly take counter business as a main point. With the continuous development of the internet, counter services are gradually transferred to the internet, and the financial service system is iterated faster and faster along with the change of the requirements of the internet services and innovation services, so that the system has better requirements on the throughput and high availability, and a certain number of workers are required to be configured for developing service development. Meanwhile, a large amount of operation expenses such as corresponding equipment, water and electricity charges, staff wages and the like generated by expanding system resources in response to internet flow need to be borne, and the cost is high. Such as self-service account opening, depositing and withdrawing, printing a fund flow, and the like. In order to adapt to different business scenarios, different business codes need to be developed, however, a set of programs is developed corresponding to different business scenarios, different business scenarios have the same or similar service items, and related program codes may be the same or similar, which causes a large amount of workload on one hand and a large amount of code repetition on the other hand. Until now, there has been no better solution.
Disclosure of Invention
In view of the above, it is an object of the present invention to provide a financial transaction engine with high performance, high availability, and configurable, and commercialized financial-level underlying support. The transaction engine can ensure the performance requirement of the financial-grade business system and deal with the actual situation in the landing practice, and a commercialized financial institution business system is formed. The specific scheme is as follows:
a transaction scheduling engine construction method comprises the following steps:
defining component information, and developing a program corresponding to each component, wherein the program is a package of different data and methods, the defining component information comprises defining a component inlet and outlet dictionary, the component inlet and outlet dictionary comprises functions corresponding to each component inlet and each component outlet, and an execution result of the component is transmitted to a component outlet sub-data space corresponding to each component in a component outlet data space;
combining one or more components into a service in sequence, enabling the components to complete the service when the components are executed in sequence, defining service information, wherein the service information comprises a service entrance dictionary, each service entrance dictionary comprises a function corresponding to each service entrance and each service exit, establishing a mapping relation between the component entrance and the service entrance or a component exit data space according to the component entrance dictionary and the service entrance dictionary, and establishing a mapping relation between the service exit and at least one component exit sub-data space, so that the service acquires values from the corresponding component exit sub-data space according to the assembled components thereof as output data of the service, and the output data of each service is stored in the independent service exit sub-data space in the service exit data space;
combining one or more services into a transaction, defining transaction information, wherein the transaction information comprises a transaction access dictionary, the transaction access dictionary comprises functions corresponding to transaction inlets and transaction outlets, and a mapping relation between the service inlets and the transaction inlets or the service outlets is established according to the service access dictionary and the transaction access dictionary, so that the transaction takes values from corresponding service outlet sub-data spaces as output data of the transaction according to the assembled services.
The present invention also provides an electronic device, comprising: the transaction scheduling engine building program comprises a memory and a processor, wherein the memory stores the transaction scheduling engine building program, and the transaction scheduling engine building program realizes the transaction scheduling engine building method when being executed by the processor.
The present invention also provides a computer readable storage medium storing a computer program comprising program instructions which, when executed by a processor, implement the transaction scheduling engine construction method as described above.
The present invention also provides a transaction scheduling engine, comprising:
each component corresponds to a program, the program is a package of different data and methods, the component comprises a component inlet and outlet dictionary, the component inlet and outlet dictionary comprises functions corresponding to each component inlet and each component outlet, and an execution result of the component is transmitted to a component outlet sub-data space corresponding to each component in a component outlet data space;
the service engine is used for building services, the services are formed by sequentially combining one or more components, the services are completed when the components are sequentially executed, the services comprise service inlet and outlet dictionaries, the service inlet and outlet dictionaries comprise functions corresponding to service inlets and service outlets, the mapping relation between the component inlets and the service inlets or the component outlet data spaces is built according to the component inlet and outlet dictionaries and the service inlet and outlet dictionaries, the mapping relation between the service outlets and at least one component outlet sub-data space is built, so that the components assembled by the services are taken from the corresponding component outlet sub-data spaces as output data of the services, and the output data of each service is stored in the independent service outlet sub-data spaces in the service outlet data spaces;
and the transaction engine is used for establishing a transaction, the transaction is formed by combining one or more services, the transaction comprises a transaction access dictionary, the transaction access dictionary comprises functions corresponding to each transaction inlet and each transaction outlet, and a mapping relation between the service inlet and the transaction inlet or the service outlet data space is established according to the service access dictionary and the transaction access dictionary, so that the transaction takes values from the corresponding service outlet sub-data space as output data of the transaction according to the assembled services.
The present invention also provides a service framework system, including:
the service middle platform layer comprises:
each component corresponds to a program, the program is a package of different data and methods, the component comprises a component inlet and outlet dictionary, the component inlet and outlet dictionary comprises functions corresponding to each component inlet and each component outlet, and an execution result of the component is transmitted to a component outlet sub-data space corresponding to each component in a component outlet data space;
the service engine is used for building services, the services are formed by sequentially combining one or more components, the services are completed when the components are sequentially executed, the services comprise service inlet and outlet dictionaries, the service inlet and outlet dictionaries comprise functions corresponding to service inlets and service outlets, the mapping relation between the component inlets and the service inlets or the component outlet data spaces is built according to the component inlet and outlet dictionaries and the service inlet and outlet dictionaries, the mapping relation between the service outlets and at least one component outlet sub-data space is built, so that the components assembled by the services are taken from the corresponding component outlet sub-data spaces as output data of the services, and the output data of each service is stored in the independent service outlet sub-data spaces in the service outlet data spaces;
the service layer is used for constructing the micro-service by calling the service of the platform layer in the service;
and the micro-service establishes connection with the application layer through the gateway so as to be called by the application layer.
The invention also provides a transaction scheduling method, which applies the transaction scheduling engine to carry out the following steps:
after receiving the transaction request, the transaction scheduling engine schedules the corresponding transaction according to the transaction code in the message;
the transaction is subjected to security verification according to the transaction definition information, the assembled service is dispatched according to the transaction after the security verification is passed, the assembled components are dispatched according to the assembly sequence by the service,
the service entrance acquires service input data from the transaction entrance or the service exit, the service exit data is put into the service exit data space after the service operation is finished, the component entrance acquires component input data from the service entrance or the component exit, and the component exit data is put into the component exit data space after the component operation is finished;
and (4) taking the value of the transaction from the service outlet space, generating transaction outlet data and returning the transaction outlet data to the transaction scheduling engine.
The invention provides the infrastructure capability of the transaction mode of the financial platform, the system can realize a safe, stable, reliable, efficient and quick transaction system only by making relevant dynamic configuration, is simple and easy to use, does not need to use hard coding to realize business function service, simplifies the business development process, helps users realize the transaction system in the integral financial platform, and saves a large amount of development and implementation cost. The method solves the problems of configuration and granularity of business models, productions and productions components in the financial industry, can realize componentization dynamic configuration, is suitable for rapid change and iteration of business requirements in the financial industry, realizes multidimensional transaction, service measurement and unified programming interface, and also simplifies the difficulty and development cost of creating a large-scale high-availability and high-reliability financial transaction system.
Drawings
The above features and technical advantages of the present invention will become more apparent and readily appreciated from the following description of the embodiments thereof taken in conjunction with the accompanying drawings.
FIG. 1 is a step diagram illustrating a transaction scheduling engine construction method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a transaction engine that represents an embodiment of the present invention;
FIG. 3 is a schematic diagram of a service engine that represents an embodiment of the present invention;
FIG. 4 is a schematic diagram of a business framework system illustrating an embodiment of the invention;
FIG. 5 is a hardware configuration diagram of an electronic apparatus according to an embodiment of the present invention;
fig. 6 is a block configuration diagram showing a transaction scheduling engine construction program according to an embodiment of the present invention.
Detailed Description
Embodiments of a transaction scheduling engine and a method of constructing the same according to the present invention will be described below with reference to the accompanying drawings. Those of ordinary skill in the art will recognize that the described embodiments can be modified in various different ways, or combinations thereof, without departing from the spirit and scope of the present invention. Accordingly, the drawings and description are illustrative in nature and not intended to limit the scope of the claims. Furthermore, in the present description, the drawings are not to scale and like reference numerals refer to like parts.
As shown in fig. 1, the transaction scheduling engine construction method of the present embodiment includes the following steps:
step S1, component information is defined, and a program corresponding to each component is developed (including at least generating a component code class and filling in a service code). The components do not have service attributes, only have input and output, have no direct relation with specific services, and are encapsulation of different data and methods. For example, the component may be a drop-down menu component, a button component, a navigation component, a pop-up window component, and the like for interface presentation, or may be a report component, a chart component, a curve drawing component, and the like for data presentation. The definition component information comprises definition component code, component description and other basic configuration information, and the definition component information further comprises a definition component access dictionary, wherein the definition component access dictionary comprises functions corresponding to each component inlet and each component outlet. For example, a button component defines functions of its component entry and component exit, i.e., the button component can be called, and different data can be input through the component entry and different button forms can be output from the component exit. And transmitting the execution result of the component to a component outlet word data space corresponding to each component of the component outlet data space.
Step S2, defining service information, including basic configuration information such as service code and service description, and making assembly configuration of service and components. The service has a service attribute that completes a service item, such as a balance inquiry service, a loan approval service, a house passing service, and the like. In the balance inquiry service, a plurality of components may be involved, for example, the components for interface presentation described above are included, the components for data inquiry are included, and the components for data presentation are included.
The service and the assembly configuration of the components refer to the combination of one or more components into one service, and the same component can be used among services, for example, each service comprises the components of the same interface display. In one service, the components are configured in a sequential execution manner such that a service function is completed after sequential execution. For example, the balance inquiry service is composed of a graphical interface component, a data inquiry component and a data display component, and in the balance inquiry service, the data inquiry component, the interface display component and the data display component are sequentially executed. Defining the service information further comprises configuring a service entrance and exit dictionary of the service, wherein the service entrance and exit dictionary comprises functions corresponding to each service entrance and each service exit for transaction calling.
And establishing a mapping relation between the component inlet and the service inlet or the component outlet data space according to the component inlet and outlet dictionary and the service inlet and outlet dictionary, so that the component can take values from the service inlet or the component outlet data space as input data. The operational result data for each component is stored in a separate component outlet sub-data space in the component outlet data space. And establishing a mapping relation between the service outlet and at least one component outlet sub-data space, so that the service takes the value from the corresponding component outlet sub-data space as the output data of the service according to the assembled components. The operation result data of each service is stored in a separate service outlet sub data space in the service outlet data space.
The components contained in different services may be the same or different, and their corresponding output results may also be different. The component export is defined according to the service export.outparam maps with the service export, e.g., service export.outparam = component 01 export.outparam 1, generates service export data from values in the component export data space. That is, the integrated execution results of the components are obtained at the service outlets according to different needs, for example, the combination of the service outlet outparam = component 01.outparam1 and the component 02.outparam 1. As long as the mapping relationship between the service outlet and the sub-data space of each component outlet is configured.
Step S3, transaction information is defined, the transaction information includes some attribute information corresponding to the transaction and is used for safety verification, and relevant safety verification is carried out according to the transaction information after the transaction is executed. The system also comprises transaction codes, and each transaction corresponds to one transaction code so as to be convenient for scheduling the corresponding transaction according to the transaction codes in the message after receiving the transaction request.
The defining of the transaction information further comprises defining a transaction entrance and exit dictionary, and the transaction entrance and exit dictionary comprises functions corresponding to the transaction entrances and the transaction exits. And establishing a mapping relation between the service entrance and a transaction entrance or service exit data space according to the service entrance dictionary and the transaction entrance dictionary, so that the service entrance can take values from the transaction entrance or service exit data space as input data. Service 01. infiram takes values from the transaction entry and service 02. infiram takes values from the service exit data space as in fig. 2. And establishing a mapping relation between the transaction and at least one service outlet sub-data space, so that the value of the transaction from the corresponding service outlet sub-data space can be taken as a transaction result.
As shown in fig. 3, when a component is serviced, the code class of the assembled component is scheduled according to the assembly information, in the component scheduling, a component entry takes a value from a service entry space or a component exit data space, the service entry takes input data from a transaction entry space or a service exit data space, the component finishes operating and puts operating result data into a component exit sub-data space of the component exit data space (for example, a component exit data bus), and each component exit sub-data space is independent; and after the service operation is finished, putting the service outlet data into the service outlet sub-data space of the service outlet data space, wherein each service outlet sub-data space is independent.
For example, as shown in fig. 3, for a service, the data input by the service portal includes parameters of an inline 1 (service portal. inline 1), an inline 2 (service portal. inline 2), and …, and the corresponding components in the service are sequentially executed. Taking a certain parameter, inparam1 as an example, the execution process of the parameter in the component is described. The input parameter for component 01 is component 01. infiram = service entry. infiram 1. The output data of component 01 is stored for component 01.outparam1 on the component egress data bus. The component 02 takes the component 01.outparam1 from the component egress data bus as an input to the component 02, but of course, data may be selected from the service entries, inparam1, service entries, inparam2, … as an input to the component 02, or values may be taken from both. The output component 02.outparam1 of component 02 is stored on the component egress data bus, and so on.
Similarly, the components are executed in sequence corresponding to the service entry, inline 2, service entry, inline 3, …, and values are taken from the component exit data space as the result data of the service.
Further, in the transaction and service group configuration, a transaction may include a plurality of services, and the services may be configured to be executed sequentially, or may be executed concurrently, or may be executed sequentially and concurrently. And configuring a transaction entry map and a transaction exit map for the transaction composed of the assembled services.
For example, the house property transaction may include house check service, house purchase qualification check service, payment service, house property passing service. Wherein, the house checking service, the house purchasing qualification checking service, the payment service and the house property user passing service are executed in sequence. Each service comprises a plurality of components, for example, the house verification service may include a house basic information comparison component and a house dispute query component, and the house basic information may be a house address, a house type, a house ownership, and the like. The house dispute includes the conditions of checking whether the house has court sealing, mortgage, credit dispute and the like.
As shown in fig. 2, the sequential execution of the service is similar to the sequential execution of the components, and the input parameter corresponding to the service 01 is service 01. infiram = transaction entry. infiram 1. The output service 01.outparam1 of service 01 is stored on the service egress data bus. Service 02 extracts data from the service egress data bus or transaction ingress as input to service 02. The output service 02 of service 02.outparam1 is stored on the service egress data bus, and so on.
The concurrent execution of the service refers to a transaction entry, an spar 1, a transaction entry, an spar 2 and a transaction entry, spar 3 …, which are respectively input into the service 01, the service 02 and the service 03 …, and respectively obtain a service 01 exit, an outlaram 1, a service 02 exit, an outlaram 2 and a service 03 exit, outlaram 3.
Of course, both sequential and concurrent may be included. For example, the first services are executed sequentially, the middle services are executed concurrently, and the results of concurrent execution continue to complete sequential execution with the preceding and following services.
And the transaction execution results are obtained at a service outlet according to different needs, for example, the transaction outlet outparam = service 01 outlet outparam 1. Only the mapping relationship between the transaction outlet and each service outlet is configured.
In an alternative embodiment, the transaction engine and the service engine also generate audit logs and exception records for channel analysis, call volume query and performance, failure analysis.
In an alternative embodiment, one of the transactions or services is invoked using an http (hypertext transfer protocol) call or an RPC (remote procedure call) call.
The invention also provides a transaction scheduling engine which comprises a transaction engine, a service engine and a component, wherein the transaction engine is used for building transactions, and the service engine is used for building services. The transaction comprises a transaction inlet, a transaction outlet and a transaction outlet data bus, wherein the transaction comprises a plurality of services, the services comprise a service inlet, a service outlet and a component outlet data bus, and one or more components are combined to form one service.
In the transaction, a mapping relation between a service entrance and a transaction entrance or service exit data space is established according to the service entrance dictionary and the transaction entrance dictionary, so that the service entrance can take values from the transaction entrance or service exit data space as input data. Service 01. infiram takes values from transaction entry and service 02. infiram takes values from service exit as in fig. 2. And establishing a mapping relation between the transaction and at least one service outlet sub-data space, so that the value of the transaction from the corresponding service outlet sub-data space can be taken as a transaction result.
A transaction may comprise multiple services, may be assembled with multiple services to be performed sequentially, or may be performed concurrently, or may be performed sequentially and concurrently. And configuring an entry map and a transaction exit map for the transaction composed of each assembled service. For example, the house property transaction may include house check service, house purchase qualification check service, payment service, house property passing service. Wherein, the house checking service, the house purchasing qualification checking service, the payment service and the house property user passing service are executed in sequence. Each service comprises a plurality of components, for example, the house verification service may include a house basic information comparison component and a house dispute query component, and the house basic information may be a house address, a house type, a house ownership, and the like. The house disputes include verifying whether houses are court sealed, mortgage, credit disputes, etc.
In the sequential execution, as shown in fig. 2, the input parameter corresponding to the service 01 is service 01. infiram = transaction entry. infiram 1. The output service 01.outparam1 of service 01 is stored on the service egress data bus. Service 02 extracts data from the service egress data bus or transaction ingress as input to service 02. The output service 02 of service 02.outparam1 is stored on the service egress data bus, and so on.
Concurrent execution refers to a transaction entry, an inline 1, a transaction entry, an inline 2, and a transaction entry, inline 3 …, respectively input into the service 01, the service 02, and the service 03 …, respectively, to obtain a service 01 exit, an outbound param1, a service 02 exit, an outbound param2, and a service 03 exit, an outbound param 3.
Of course, both sequential and concurrent may be included. For example, the first services are executed sequentially, the middle services are executed concurrently, and the results of concurrent execution continue to complete sequential execution with the preceding and following services.
And the transaction execution result is obtained in the service export data space according to different requirements, for example, the transaction export. Only the mapping relation between the transaction outlet and each service outlet sub-data space is configured.
The service engine defines service information, and the service information includes a service entrance and exit dictionary for configuring services, wherein the service entrance and exit dictionary includes functions corresponding to service entrances and service exits for transaction calling. And establishing a mapping relation between the component inlet and the service inlet or the component outlet data space according to the component inlet and outlet dictionary and the service inlet and outlet dictionary, so that the component can take values from the service inlet or the component outlet data space as input data. The operational result data for each component is stored in a separate component sub-data space in the component outlet data space. And establishing a mapping relation between the service outlet and at least one component outlet sub-data space, so that the value of the service is taken from the corresponding component sub-data space as the output data of the service according to the assembled components. The operation result data of each service is stored in the service sub data space independent from each other in the service outlet data space.
The service has a service attribute that completes a service item, such as a balance inquiry service, a loan approval service, a house passing service, and the like. In the balance inquiry service, a plurality of components may be involved, for example, the components for interface presentation described above are included, the components for data inquiry are included, and the components for data presentation are included.
One or more components are combined into one service, and the same component can be used among the services, for example, each service comprises the components of the same interface display. In one service, the components are configured in a sequential execution manner such that a service function is completed after sequential execution. An ingress map and a service egress map of a service formed by each assembled component are configured. For example, a balance inquiry service is composed of a graphical interface component, a data inquiry component and a data display component, an entry mapping and an exit mapping are configured for the balance inquiry service, the balance inquiry service can be called, and after the balance inquiry service is called through an entry, all components in the balance inquiry service are executed in sequence. For example, in the balance inquiry service, the data inquiry component, the interface presentation component and the data presentation component are sequentially executed.
As shown in fig. 1, when a service engine schedules components, the code classes of the assembled components are scheduled in sequence according to assembly information, a component entry in component scheduling takes a value from a service entry or a component exit data space, the service entry takes input data from a transaction entry or a service exit data space, the component exit data needs to be put into a corresponding component exit sub-data space of the component exit data space after the component operation is finished, and each component exit sub-data space is independent; and after the service operation is finished, putting the service outlet data into service outlet data spaces, wherein each service outlet data space is independent.
For example, for one service, data input by a service portal includes parameters of the parameter of 1 (service portal of 1), the parameter of the service of the. The input parameter for component 01 is component 01. infiram = service entry. infiram 1. The output data of component 01 is stored for component 01.outparam1 on the component egress data bus. The component 02 takes the component 01.outparam1 from the component egress data bus as an input to the component 02, but of course, data may be selected from the service entries inparam1, service entries inparam2, … as an input to the component 02, or values may be taken from both. The output component 02.outparam1 of component 02 is stored on the component egress data bus, and so on.
Similarly, the components are executed in sequence corresponding to the service entry, inline 2, service entry, inline 3, …, and values are taken from the component exit data space as the result data of the service.
The components contained in different services may be the same or different, and their corresponding output results may also be different. And after service scheduling is finished, taking values from the component outlet data space according to the service outlet dictionary definition and the service outlet mapping, and generating service outlet data. That is, the integrated execution results of the components are obtained at the service outlets according to different needs, for example, the service outlet outparam = component 01. For example, the service outlet a combination of component 01.outparam1 and component 02.outparam 1. As long as the mapping relationship between the service outlet and each component outlet is configured.
Each component comprises component information and a component access dictionary, and each component corresponds to an execution program. The components do not have service attributes, only have input and output, have no direct relation with specific services, and are encapsulation of different data and methods. Defining component information means that the component inlet and outlet dictionary comprises functions corresponding to each component inlet and each component outlet.
The invention also provides a business framework system which comprises a business middle platform layer, a service layer and an application layer and can provide system configuration for a plurality of businesses. The service middlebox layer comprises the services and the components, so that the middlebox layer can provide common capability and support a plurality of services. As shown in fig. 4, the service middleware layer includes a global call packet, a subsystem call packet, and a sub-domain call packet, where the global call packet includes services that can be called by all services. The subsystem calling package is divided according to the field design and used for calling the services in different fields, and the subdomain calling package is used for calling the next-level service in the fields.
In the service layer, the micro-service can be constructed by calling the subdomain calling packet of the service layer, and different micro-services can be constructed by calling different calling packets. And each micro service can be connected with a counter system, a channel system, a transmission system and the like of the application layer through a gateway for calling.
The invention also provides a transaction scheduling method, which applies the transaction scheduling engine to carry out the following steps:
after receiving the transaction request, the transaction scheduling engine schedules the corresponding transaction according to the transaction code in the message;
the transaction is subjected to security verification according to the transaction definition information, the assembled service is dispatched according to the transaction after the security verification is passed, the assembled components are dispatched according to the assembly sequence by the service,
the service entrance acquires service input data from the transaction entrance or the service exit, the service exit data is put into the service exit data space after the service operation is finished, the component entrance acquires component input data from the service entrance or the component exit, and the component exit data is put into the component exit data space after the component operation is finished;
and (4) taking the value of the transaction from the service outlet space, generating transaction outlet data and returning the transaction outlet data to the transaction scheduling engine.
The invention also provides an electronic device, which is shown in fig. 5 and is a schematic diagram of a hardware architecture of an embodiment of the electronic device of the invention. In the present embodiment, the electronic device 2 is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction. For example, the server may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster composed of a plurality of servers). As shown in fig. 5, the electronic device 2 at least includes, but is not limited to, a memory 21 and a processor 22 which are communicatively connected to each other through a system bus, wherein the memory 21 stores therein a transaction scheduling program, and the transaction scheduling program implements the transaction scheduling method as described above when executed by the processor.
Wherein: the memory 21 includes at least one type of computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. The processor 22 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments.
The transaction scheduling engine builder 20 stored in the memory 21 may be divided into one or more program modules stored in the memory 21 and executable by one or more processors (in this embodiment, the processor 22) to accomplish the present invention. For example, fig. 6 shows a schematic diagram of the transaction scheduling engine building program module, in this embodiment, the transaction scheduling engine building program 20 may be divided into a component building module 201, a service building module 202, and a transaction building module 203, where the program module referred to in the present invention refers to a series of computer program instruction segments capable of performing a specific function, and is more suitable than a program for describing the execution process of the transaction scheduling engine building program in the electronic device 2. The following description will specifically describe specific functions of the program modules.
The component construction module 201 is configured to define component information, and develop a program corresponding to each component, where the program is a package of different data and methods, the component information includes a component entry and exit dictionary, the component entry and exit dictionary includes functions corresponding to each component entry and each component exit, and an execution result of a component is transmitted to a component exit subspace corresponding to each component in a component exit data space;
the service construction module 202 is configured to sequentially combine one or more components into a service, so that the component completes the service when being sequentially executed, and defines service information, where the service information includes a service entry and exit dictionary, where the service entry and exit dictionary includes functions corresponding to each service entry and each service exit, and a mapping relationship between a component entry and a service entry or a component exit data space is established according to the component entry and exit dictionary and the service entry and exit dictionary, and a mapping relationship between a service exit and at least one component exit sub-data space is established, so that the service takes values from the corresponding component exit sub-data space according to the components assembled by the service as output data of the service, and the output data of each service is stored in a respective independent service exit sub-data space in the service exit data space;
the transaction construction module 203 is configured to combine one or more services into a transaction, define transaction information, where the transaction information includes a transaction entrance dictionary, the transaction entrance dictionary includes functions corresponding to each transaction entrance and each transaction exit, and establish a mapping relationship between a service entrance and a transaction entrance or a service exit data space according to the service entrance dictionary and the transaction entrance dictionary, so that the transaction takes a value from a corresponding service exit sub-data space according to an assembled service as output data of the transaction.
The present invention also provides a computer readable storage medium storing a computer program comprising program instructions which, when executed by a processor, implement the transaction scheduling engine construction method as described above.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A transaction scheduling engine construction method is characterized by comprising the following steps:
defining component information, and developing a program corresponding to each component, wherein the program is a package of different data and methods, the defining component information comprises defining a component inlet and outlet dictionary, the component inlet and outlet dictionary comprises functions corresponding to each component inlet and each component outlet, and an execution result of the component is transmitted to a component outlet sub-data space corresponding to each component in a component outlet data space;
combining one or more components into a service in sequence, enabling the components to complete the service when the components are executed in sequence, defining service information, wherein the service information comprises a service entrance dictionary, each service entrance dictionary comprises a function corresponding to each service entrance and each service exit, establishing a mapping relation between the component entrance and the service entrance or a component exit data space according to the component entrance dictionary and the service entrance dictionary, and establishing a mapping relation between the service exit and at least one component exit sub-data space, so that the service acquires values from the corresponding component exit sub-data space according to the assembled components thereof as output data of the service, and the output data of each service is stored in the independent service exit sub-data space in the service exit data space;
combining one or more services into a transaction, defining transaction information, wherein the transaction information comprises a transaction access dictionary, the transaction access dictionary comprises functions corresponding to transaction inlets and transaction outlets, and a mapping relation between the service inlets and the transaction inlets or the service outlets is established according to the service access dictionary and the transaction access dictionary, so that the transaction takes values from corresponding service outlet sub-data spaces as output data of the transaction according to the assembled services.
2. The transaction scheduling engine construction method of claim 1,
the transaction information also comprises transaction codes corresponding to the transactions one by one, the corresponding transactions are scheduled according to the transaction codes after the transaction request is received,
the service information also comprises service codes corresponding to the services one by one, the corresponding services are scheduled according to the service codes after the service request is received,
the component information also includes component codes corresponding to the components one to one, and the corresponding components are scheduled according to the component codes after receiving the component requests.
3. The transaction scheduling engine construction method of claim 1,
and calling the transaction and the service by adopting an http calling mode or an RPC calling mode.
4. The transaction scheduling engine construction method of claim 1,
a transaction contains multiple services that are executed sequentially, or concurrently.
5. The transaction scheduling engine construction method of claim 1,
the component egress data space and the service egress data space are in the form of data buses.
6. An electronic device, comprising: a memory having stored therein a transaction scheduling engine building program that, when executed by the processor, implements the transaction scheduling engine building method of claim 1.
7. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, implement the transaction scheduling engine construction method of any one of claims 1 to 5.
8. A transaction scheduling engine, comprising:
each component corresponds to a program, the program is a package of different data and methods, the component comprises a component inlet and outlet dictionary, the component inlet and outlet dictionary comprises functions corresponding to each component inlet and each component outlet, and an execution result of the component is transmitted to a component outlet sub-data space corresponding to each component in a component outlet data space;
the service engine is used for building services, the services are formed by sequentially combining one or more components, the services are completed when the components are sequentially executed, the services comprise service inlet and outlet dictionaries, the service inlet and outlet dictionaries comprise functions corresponding to service inlets and service outlets, the mapping relation between the component inlets and the service inlets or the component outlet data spaces is built according to the component inlet and outlet dictionaries and the service inlet and outlet dictionaries, the mapping relation between the service outlets and at least one component outlet sub-data space is built, so that the components assembled by the services are taken from the corresponding component outlet sub-data spaces as output data of the services, and the output data of each service is stored in the independent service outlet sub-data spaces in the service outlet data spaces;
and the transaction engine is used for establishing a transaction, the transaction is formed by combining one or more services, the transaction comprises a transaction access dictionary, the transaction access dictionary comprises functions corresponding to each transaction inlet and each transaction outlet, and a mapping relation between the service inlet and the transaction inlet or the service outlet data space is established according to the service access dictionary and the transaction access dictionary, so that the transaction takes values from the corresponding service outlet sub-data space as output data of the transaction according to the assembled services.
9. A business framework system, comprising:
the service middle platform layer comprises:
each component corresponds to a program, the program is a package of different data and methods, the component comprises a component inlet and outlet dictionary, the component inlet and outlet dictionary comprises functions corresponding to each component inlet and each component outlet, and an execution result of the component is transmitted to a component outlet sub-data space corresponding to each component in a component outlet data space;
the service engine is used for building services, the services are formed by sequentially combining one or more components, the services are completed when the components are sequentially executed, the services comprise service inlet and outlet dictionaries, the service inlet and outlet dictionaries comprise functions corresponding to service inlets and service outlets, the mapping relation between the component inlets and the service inlets or the component outlet data spaces is built according to the component inlet and outlet dictionaries and the service inlet and outlet dictionaries, the mapping relation between the service outlets and at least one component outlet sub-data space is built, so that the components assembled by the services are taken from the corresponding component outlet sub-data spaces as output data of the services, and the output data of each service is stored in the independent service outlet sub-data spaces in the service outlet data spaces;
the service layer is used for constructing the micro-service by calling the service of the platform layer in the service;
and the micro-service establishes connection with the application layer through the gateway so as to be called by the application layer.
10. A transaction scheduling method, characterized in that, applying the transaction scheduling engine of claim 8, the following steps are performed:
after receiving the transaction request, the transaction scheduling engine schedules the corresponding transaction according to the transaction code in the message;
the transaction is subjected to security verification according to the transaction definition information, the assembled service is dispatched according to the transaction after the security verification is passed, the assembled components are dispatched according to the assembly sequence by the service,
the service entrance acquires service input data from the transaction entrance or the service exit, the service exit data is put into the service exit data space after the service operation is finished, the component entrance acquires component input data from the service entrance or the component exit, and the component exit data is put into the component exit data space after the component operation is finished;
and (4) taking the value of the transaction from the service outlet space, generating transaction outlet data and returning the transaction outlet data to the transaction scheduling engine.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010033050.5A CN110825359B (en) | 2020-01-13 | 2020-01-13 | Transaction scheduling engine and construction and scheduling method, system, device and medium thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010033050.5A CN110825359B (en) | 2020-01-13 | 2020-01-13 | Transaction scheduling engine and construction and scheduling method, system, device and medium thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110825359A true CN110825359A (en) | 2020-02-21 |
| CN110825359B CN110825359B (en) | 2020-05-08 |
Family
ID=69546625
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010033050.5A Active CN110825359B (en) | 2020-01-13 | 2020-01-13 | Transaction scheduling engine and construction and scheduling method, system, device and medium thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110825359B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111736977A (en) * | 2020-07-21 | 2020-10-02 | 成都新希望金融信息有限公司 | Central dispatching method and system for multiple middle stations |
| CN113986249A (en) * | 2021-11-26 | 2022-01-28 | 中国银行股份有限公司 | Financial service interface external embedding method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101373474A (en) * | 2008-09-02 | 2009-02-25 | 北京开拓天际信息技术有限公司 | Magnanimity data real time processing structure and real time processing platform following with necessaries for the same |
| CN101877109A (en) * | 2010-04-08 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Application system tool set based on online banking service platform |
| US20180150379A1 (en) * | 2016-11-28 | 2018-05-31 | Daniel Ratiu | Method and system of verifying software |
-
2020
- 2020-01-13 CN CN202010033050.5A patent/CN110825359B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101373474A (en) * | 2008-09-02 | 2009-02-25 | 北京开拓天际信息技术有限公司 | Magnanimity data real time processing structure and real time processing platform following with necessaries for the same |
| CN101877109A (en) * | 2010-04-08 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Application system tool set based on online banking service platform |
| US20180150379A1 (en) * | 2016-11-28 | 2018-05-31 | Daniel Ratiu | Method and system of verifying software |
Non-Patent Citations (1)
| Title |
|---|
| 孙江涛: "基于CICS中间件的银行财政支付系统的设计与实现", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111736977A (en) * | 2020-07-21 | 2020-10-02 | 成都新希望金融信息有限公司 | Central dispatching method and system for multiple middle stations |
| CN113986249A (en) * | 2021-11-26 | 2022-01-28 | 中国银行股份有限公司 | Financial service interface external embedding method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110825359B (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9501778B2 (en) | Delivering personalized recommendations that relate to transactions on display | |
| US9129052B2 (en) | Metering resource usage in a cloud computing environment | |
| US10839160B2 (en) | Ontology-based automatic bootstrapping of state-based dialog systems | |
| US20110138047A1 (en) | Provisioning services using a cloud services catalog | |
| JP2022553663A (en) | Content identification method, system and program for tabular data using machine learning | |
| CN110825359B (en) | Transaction scheduling engine and construction and scheduling method, system, device and medium thereof | |
| US11455337B2 (en) | Preventing biased queries by using a dictionary of cause and effect terms | |
| CN111768322A (en) | Charitable service platform system | |
| US20200302350A1 (en) | Natural language processing based business domain modeling | |
| US20140278356A1 (en) | Smart posting with data analytics | |
| US20180089677A1 (en) | Scalable credit card system | |
| CN113448848B (en) | Conversion method and device based on use case method, electronic equipment and storage medium | |
| US11288322B2 (en) | Conversational agents over domain structured knowledge | |
| US10990413B2 (en) | Mainframe system structuring | |
| US11100556B2 (en) | Scenario enhanced search with product features | |
| US20200192778A1 (en) | Real-time collaboration dynamic logging level control | |
| CN115760013A (en) | Operation and maintenance model construction method and device, electronic equipment and storage medium | |
| CN113989046A (en) | Transaction processing method, apparatus, electronic device, storage medium, and program product | |
| US11250215B2 (en) | Form-based transactional conversation system design | |
| CN104519096B (en) | Method and system for the deployment services in cloud computing system | |
| US12045825B2 (en) | Linguistic transformation based relationship discovery for transaction validation | |
| Ramadhani | Design and Implementation of Mobile Native Application | |
| US20230267278A1 (en) | Context-based response generation | |
| US11720533B2 (en) | Automated classification of data types for databases | |
| US20230214276A1 (en) | Artificial Intelligence Model Management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |