A financial transaction monitoring system based on B / S architecture

Abstract

The present invention discloses a financial transaction monitoring system with a B / S architecture, which counts transaction data of concern to customers, intercepts abnormal transaction behaviors, reduces transaction risks and operation and maintenance costs, and ensures transaction reliability and transaction security. The technical solution is as follows: the system includes a front-end and a back-end server, wherein the back-end server is configured to generate a processor instance upon receiving each front-end request, the processor instance is used to process the front-end request, and after the processing is completed, the processing result is returned to the back-end server and automatically destroyed; the front-end configuration is as follows: the vuex state management mode is introduced in the vue framework, and multiple components share the state in the threshold storage and the basic data storage of the transaction product contract.

Description

Technical Field

[0001] The present invention relates to financial transaction software, and in particular to a financial transaction monitoring system with a B / S architecture. Background Art

[0002] In high-frequency and high-performance financial trading software, the monitoring system of the trading software plays a vital role in order to ensure the stable operation of the trading software. The monitoring system includes system monitoring and business monitoring and risk control. The data such as CPU usage, disk space usage, and memory usage that the system monitoring focuses on are related to the software performance. When the data is large, the execution efficiency of the software will be reduced. When customers use the trading software to trade, the business monitoring and risk control can simultaneously summarize and monitor the transaction data and intercept abnormal transactions, thereby avoiding transaction risks.

[0003] Currently, the industry lacks a monitoring system that can monitor both customers' transaction data and the operation status of trading software. Summary of the invention

[0004] A brief summary of one or more aspects is given below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its only purpose is to give some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0005] The purpose of the present invention is to solve the above problems and provide a financial transaction monitoring system with a B / S architecture, which counts transaction data of customer concern and intercepts abnormal transaction behaviors, thereby reducing transaction risks and operation and maintenance costs, and ensuring transaction reliability and security.

[0006] The technical solution of the present invention is: the present invention discloses a financial transaction monitoring system with a B / S architecture, the system includes a front-end server and a back-end server, wherein:

[0007] The backend server is configured to: generate a processor instance upon receiving each frontend request, the processor instance is used to process the frontend request, and after the processing is completed, the processing result is returned to the backend server and automatically destroyed;

[0008] The front-end configuration is: the vuex state management mode is introduced in the vue framework, and multiple components share the state in threshold storage and basic data storage of trading product contracts.

[0009] According to an embodiment of the financial transaction monitoring system with a B / S architecture of the present invention, the multiple processor instances run in parallel.

[0010] According to an embodiment of the financial transaction monitoring system of the B / S architecture of the present invention, the backend server is a horizontally scalable asynchronous http and web_socket server.

[0011] According to an embodiment of the financial transaction monitoring system of the B / S architecture of the present invention, the backend server includes a combination of any of the following modules:

[0012] Service module, used to process monitoring requests;

[0013] Public service module, used to handle general requests;

[0014] The risk service module is used to process risk control requests.

[0015] According to one embodiment of the financial transaction monitoring system of the B / S architecture of the present invention, the back-end server can be horizontally expanded by using the importlib module of python to reference the new function code module to the asynchronous http and web_socket servers, and dynamically load the new function code module at runtime.

[0016] According to one embodiment of the financial transaction monitoring system with B / S architecture of the present invention, the back-end server is an asynchronous http and web_socket server, which means that when processing http and web_socket requests, Python's asynchronous module is called to process the requests so that the earlier requests will not block the reception and processing of later requests.

[0017] According to an embodiment of the financial transaction monitoring system of the B / S architecture of the present invention, the back-end server further includes any combination of the following modules:

[0018] Log reporting module, used to analyze logs in real time and enter them into the database;

[0019] Database reporting module, used to write file data into the database;

[0020] The calculation module is used to process the calculation work, calculate the required information according to the data in the database, and write the calculated information into the database, wherein the database stores the unprocessed transaction data generated by the transaction software;

[0021] The system status monitoring module is used to monitor the system operation status of the machine and store the data in the database.

[0022] According to one embodiment of the financial transaction monitoring system of the B / S architecture of the present invention, the vuex state management mode of the system front end is further configured as follows: during the execution of a vue, a method is triggered by a click event. When there is asynchrony, vuex triggers the method in the operation event by sending an instruction. The submission action in the operation event triggers the method in the transition event. The method in the transition event of vuex is directly triggered in the component to change the state. The changed state is updated to the view through the rendering function.

[0023] According to an embodiment of the financial transaction monitoring system of the B / S architecture of the present invention, the system also includes a processing flow for processing monitoring data on the browser, which further includes:

[0024] Step S1: In the interface layer, the front-end browser communicates with the Python backend through http and WebSocket;

[0025] Step S2: monitor the vue framework used in the front-end display;

[0026] Step S3: Obtain system monitoring indicators through the interface;

[0027] Step S4: Obtain business monitoring risk control indicators through the interface;

[0028] Step S5: respectively determine the size relationship between the obtained system monitoring indicators, business monitoring risk control indicators and their corresponding preset monitoring thresholds, and trigger the execution of step S6 when the system monitoring indicator exceeds the corresponding monitoring threshold, and trigger the execution of step S7 when the business monitoring risk control indicator exceeds the corresponding monitoring threshold. If neither the system monitoring indicator nor the business monitoring risk control indicator exceeds their respective monitoring thresholds, return to step S2 to maintain background communication and continue indicator monitoring;

[0029] Step S6: The front-end browser issues an early warning prompt, and then executes step S8;

[0030] Step S7: The front-end browser issues an early warning prompt, and then executes step S9;

[0031] Step S8: The operation and maintenance personnel troubleshoot the system monitoring indicators according to the early warning prompts;

[0032] Step S9: Determine whether the business indicators in the transaction process exceed the set risk control threshold. If the risk control threshold is exceeded, a transaction risk control warning is triggered, the transaction behavior is restricted, the risk control interception is triggered, and step S10 is continued;

[0033] Step S10: After the transaction risk control warning is triggered, the trader processes the transaction according to the risk control prompt content and lifts the current risk control transaction restrictions.

[0034] Compared with the prior art, the present invention has the following beneficial effects: the system of the present invention summarizes and monitors the indicators of concern to operation and maintenance personnel and traders in the trading software and trading process, and issues warnings by highlighting indicator data, pop-up prompts, and sound reminders, which facilitates the operation and maintenance personnel to troubleshoot problems and reduces operation and maintenance costs; it facilitates traders to view data such as funds, positions, and market-making obligation completion during the trading process, and adopts risk control restrictions for improper trading operations, that is, taking measures such as warning prompts or prohibiting operations for improper operations, thereby reducing trading risks and ensuring the reliability of trading software.

[0035] On the other hand, the system of the present invention adopts B / S (Browser / Service) architecture, which has low operation and maintenance cost, simple upgrade and deployment, and significant cost savings compared to C / S architecture. The MVVM (Model-View-View-Model) mode adopted has the advantages of low coupling, reusability, and independent development compared to the MVC (Model-View-Controller) mode. The view can be changed and modified independently of the model, and the logical processing of data and page design can be developed independently.

[0036] Finally, after receiving an http or websocket request, the system of the present invention uses importlib to dynamically distribute to the requested module, and the module call adopts a dynamic loading mode, which is flexible and extensible. After the processing module runs, the memory is recycled by the system and no redundant resources are occupied. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above features and advantages of the present invention can be better understood after reading the detailed description of the embodiments of the present disclosure in conjunction with the following drawings. In the drawings, the components are not necessarily drawn to scale, and components with similar related properties or features may have the same or similar reference numerals.

[0038] Figure 1 and Figure 2 A schematic diagram of the backend structure of an embodiment of a financial transaction monitoring system with a B / S architecture of the present invention is shown.

[0039] Figure 3 A schematic diagram of front-end state management of an embodiment of a financial transaction monitoring system with a B / S architecture of the present invention is shown.

[0040] Figure 4 The flowchart of the browser processing monitoring data of an embodiment of the financial transaction monitoring system of the B / S architecture of the present invention is shown. DETAILED DESCRIPTION

[0041] The present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. Note that the aspects described below in conjunction with the accompanying drawings and specific embodiments are only exemplary and should not be construed as limiting the scope of protection of the present invention in any way.

[0042] The embodiment of the financial transaction monitoring system of the B / S architecture of the present invention includes the following Figure 1 The architecture of the backend server shown in Figure 3 The system front-end architecture shown in Figure 4 The process of processing monitoring data on the browser is shown.

[0043] Figure 1 The implementation of the back-end server in the system of the present invention is shown as follows: Figure 1 As shown, processors (Controller) 1 to N are instances of the backend server (web_app) used to process frontend requests. Each time a frontend request (http request) is received, the backend server generates a processor instance in the memory. The processor instance is used to process the received frontend request and is automatically destroyed after processing (i.e., releasing system resources). Different processor instances can run in parallel.

[0044] Each processor instance can be understood as a part of the backend server (web_app), but the processor will be generated with new front-end requests and will be automatically destroyed (i.e., release system resources) after processing the front-end request.

[0045] The backend server parses the content of the frontend request and generates a processor instance (init controller) to process the frontend request. The processor instance processes the received frontend request and returns the result to the backend server, which then returns the result to the frontend through an http request.

[0046] exist Figure 2 In the service (mm_mid_service) module, the public service (mm_mid_general_service) module and the risk service (mm_risk_service) module, each module is a web_app. These three modules are used to process different types of http and websocket requests. Among them, the service module processes monitoring requests, the public service module processes general requests such as login, and the risk service module processes risk control requests. These three modules together form a horizontally scalable asynchronous http and web_socket server, also known as a backend server.

[0047] The number of modules that make up the backend server can be increased or decreased according to the functions required by the customer. For example, if a customer does not need to monitor logs, then the log report module can be not deployed; if a customer needs new functions, new modules can also be added.

[0048] The asynchronous http and web_socket servers constructed have two major features: 1. They can be horizontally expanded without changing the existing code. The specific processing method for horizontal expansion is: use the importlib module of python to reference the new function code module (the function code module refers to the processor instance. The code of the processor instance does not care whether the request comes from http, websocket or other protocols. The processor instance only gets the parameters and processes the business according to the parameters, that is, the function) to the asynchronous http and web_socket servers, and dynamically load the new function code module at runtime. The number of loaded function code modules does not affect the running speed of the existing system, and will not conflict with the existing function code modules. Each processor instance is independent in the code. When there is a new business demand, only a new processor instance needs to be added, and there is no need to change the code of the existing processor instance. The status of each processor instance is equal. After the dynamic loading of the function code module ends, the memory occupied by it is recycled by the system, so it will not occupy excess resources. 2. The asynchronous http and web_socket servers call Python's asynchronous module (asyncio) to process http and web_socket requests so that earlier requests will not block the reception and processing of later requests (the processing limit is limited by system capacity).

[0049] exist Figure 2 In the system, the log report module, database report module, calculation module and system status monitoring module are four separate processes, and do not directly exchange data with other processes. The log report module is used to analyze logs in real time and enter the logs into the MongoDB database. The database report module is used to write file data into the MongoDB database, and the file data is, for example, system status data. The calculation module is used to process calculation work, calculate relevant information based on the latest data in the MongoDB database, and write the calculated information into the MongoDB database, wherein the MongoDB database stores unprocessed transaction data generated by the trading software, such as order records, transaction records, etc. The calculation module periodically takes out the above-mentioned transaction data from the MongoDB database and calculates the information that the user cares about, such as the total transaction volume, the total transaction amount, etc. The system status monitoring module is used to monitor the system operation status of the machine where it is located, and store the data into the MongoDB database.

[0050] In the design of the front-end of the financial transaction monitoring system with a B / S architecture in this embodiment, in order to meet the multi-page display of system and business monitoring data, the one-way mapping of data sources to views can no longer meet the needs. The system front-end of this embodiment introduces the Vuex (a state management library specially designed for Vue.js) state management mode in the Vue framework, and realizes the shared state of multiple components in the threshold storage and the basic data storage of transaction product contracts.

[0051] The implementation process of the Vuex state management mode at the front end of the system is as follows Figure 3 shown.

[0052] Vuex processes data in chronological order. During the execution of a Vuex instance, the front-end interface triggers the methods in methods through click events. When there is asynchrony, Vuex needs to trigger the methods in actions (operation events) through dispatch (sending instructions). Actions trigger the methods in mutations (transition events) through commit (submitting actions). At this time, the State state will be changed, and the changed state (State) can be updated to the view in time through the rendering function (render).

[0053] In the above process, the operation event is used to submit the transition instead of directly changing the state, and can also be used to handle some asynchronous events.

[0054] Transition events cannot directly change the state in storage, the only way to change it is by submitting the transition process.

[0055] The Vue component responds to the changed state and displays it. When asynchronous processing is required, it triggers the method in the operation event by sending instructions.

[0056] Figure 4 This is the process of processing monitoring data on a browser in the financial transaction monitoring system of the B / S architecture of this embodiment, including the following steps:

[0057] Step S1: In the interface layer, the front-end Bowser communicates with the Python backend through Http and WebSocket.

[0058] Step S2: Monitor the Vue framework used in the front-end display. Vue is a responsive data-driven, component-based, lightweight MVVM development framework that can perform two-way binding on data and update the view in time when the data changes.

[0059] Compared with the MVC (Model-View-Controller) model, the MVVM (Model-View-View-Model) model has low coupling and a component-based development approach that improves reusability and independent development efficiency.

[0060] Step S3: Obtain system monitoring indicators through the interface, including: host memory usage, host CPU usage, host disk usage, process status and other parameters.

[0061] Step S4: Obtain business monitoring risk control indicators through the interface, including: options market making obligations, futures market making obligations, quotation statistics, capital statistics, order cancellation statistics, maximum order risk control, trading authority risk control, etc.

[0062] Step S5: Determine the size relationship between the obtained system monitoring indicators, business monitoring risk control indicators and their corresponding pre-set monitoring thresholds. The monitoring threshold is set by the customer according to actual needs. When the system monitoring indicator exceeds the corresponding monitoring threshold, step S6 is triggered to execute. When the business monitoring risk control indicator exceeds the corresponding monitoring threshold, step S7 is triggered to execute. If neither the system monitoring indicator nor the business monitoring risk control indicator exceeds their respective monitoring thresholds, return to step S2 to maintain background communication and continue indicator monitoring.

[0063] Step S6: The front-end browser Browser issues an early warning prompt by highlighting the corresponding indicator parameter in orange, popping up an interface window, and sounding an early warning prompt, and then executes step S8.

[0064] Step S7: The front-end browser Browser issues an early warning prompt by highlighting the corresponding indicator parameters in orange, popping up an interface window, and sounding an early warning prompt, and then executes step S9.

[0065] Step S8: The operation and maintenance personnel troubleshoot the system monitoring indicators according to the early warning prompts.

[0066] Step S9: Determine whether the business indicators in the transaction process exceed the set risk control threshold. If the risk control threshold is exceeded, the transaction behavior is restricted by highlighting the corresponding indicator parameters in red, pop-up windows on the interface, and warning prompt sounds, triggering risk control interception, and continuing to step S10.

[0067] Step S10: After the transaction risk control warning is triggered, the trader processes the transaction according to the risk control prompt content and lifts the current risk control transaction restrictions.

[0068] Although the above methods are illustrated and described as a series of actions for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the actions, because according to one or more embodiments, some actions may occur in a different order and / or concurrently with other actions from those illustrated and described herein or not illustrated and described herein but understandable to those skilled in the art.

[0069] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of the present invention.

[0070] The various illustrative logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, processor, microprocessor, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration.

[0071] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0072] In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented as a computer program product in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk often reproduces data magnetically, while disc reproduces data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0073] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A financial transaction monitoring system based on B / S architecture, characterized in that: The system includes front-end and back-end servers, including: The backend server is configured to: generate a processor instance upon receiving each frontend request, the processor instance is used to process the frontend request, and after the processing is completed, the processing result is returned to the backend server and automatically destroyed; The front-end configuration is as follows: the vuex state management mode is introduced in the vue framework, and multiple components share the state in the threshold storage and the basic data storage of the transaction product contract; Among them, the backend server is a horizontally scalable asynchronous http and web_socket server; The horizontal scalability of the backend server is to use the importlib module of Python to reference the new function code module to the asynchronous http and web_socket servers, and dynamically load the new function code module at runtime; The system also includes a process for processing monitoring data on the browser, which further includes: Step S1: In the interface layer, the front-end browser communicates with the Python backend through http and WebSocket; Step S2: monitor the vue framework used in the front-end display; Step S3: Obtain system monitoring indicators through the interface, where the system monitoring indicators include parameters such as host memory usage, host CPU usage, host disk usage, and process status; Step S4: Obtain business monitoring risk control indicators through the interface, where the business monitoring risk control indicators include options market making obligations, futures market making obligations, quotation statistics, capital statistics, order cancellation statistics, maximum order risk control, and trading authority risk control; Step S5: respectively determine the size relationship between the obtained system monitoring indicators, business monitoring risk control indicators and their corresponding preset monitoring thresholds, and trigger the execution of step S6 when the system monitoring indicator exceeds the corresponding monitoring threshold, and trigger the execution of step S7 when the business monitoring risk control indicator exceeds the corresponding monitoring threshold. If neither the system monitoring indicator nor the business monitoring risk control indicator exceeds their respective monitoring thresholds, return to step S2 to maintain background communication and continue indicator monitoring; Step S6: The front-end browser issues an early warning prompt, and then executes step S8; Step S7: The front-end browser issues an early warning prompt, and then executes step S9; Step S8: The operation and maintenance personnel troubleshoot the system monitoring indicators according to the early warning prompts; Step S9: Determine whether the business indicators in the transaction process exceed the set risk control threshold. If the risk control threshold is exceeded, a transaction risk control warning is triggered, the transaction behavior is restricted, the risk control interception is triggered, and step S10 is continued; Step S10: After the transaction risk control warning is triggered, the trader processes the transaction according to the risk control prompt content and lifts the current risk control transaction restrictions.

2. The financial transaction monitoring system based on B / S architecture according to claim 1, characterized in that: Multiple processor instances run in parallel.

3. The financial transaction monitoring system based on B / S architecture according to claim 1, characterized in that: The backend server includes any combination of the following modules: Service module, used to process monitoring requests; Public service module, used to handle general requests; The risk service module is used to process risk control requests.

4. The financial transaction monitoring system based on B / S architecture according to claim 1, characterized in that: The backend server is an asynchronous http and web_socket server, which means that when processing http and web_socket requests, Python's asynchronous module is called to process the requests so that the first request will not block the reception and processing of later requests.

5. The financial transaction monitoring system based on B / S architecture according to claim 1, characterized in that: The backend server also includes any combination of the following modules: Log reporting module, used to analyze logs in real time and enter them into the database; Database reporting module, used to write file data into the database; The calculation module is used to process the calculation work, calculate the required information according to the data in the database, and write the calculated information into the database, wherein the database stores the unprocessed transaction data generated by the transaction software; The system status monitoring module is used to monitor the system operation status of the machine and store the data in the database.

6. The financial transaction monitoring system based on B / S architecture according to claim 1, characterized in that: The vuex state management mode of the system front end is further configured as follows: during the execution of a vue, a method is triggered by a click event. When there is asynchrony, vuex triggers the method in the operation event by sending instructions. The submission action in the operation event triggers the method in the transition event. The method in the transition event of vuex is triggered directly in the component to change the state. The changed state is updated to the view through the rendering function.

Images