Request processing method and request processing device

Abstract

The invention provides a request processing method and a request processing device. The request processing method comprises the following steps: receiving a request from a terminal through an application interface of an application layer of a server; calling a target service subsystem from a plurality of service subsystems of the server to process the request according to service system information included in the request, wherein the multiple service subsystems are independent of each other, and the target service subsystem is at least one service subsystem in multiple service subsystems. Through the technical scheme, a data integration mode can be broken, and each subsystem can be integrated without using data as the center, so the code of each subsystem is reduced, and the maintenance efficiency, the safety and the extensibility of the subsystem are improved.

Description

technical field [0001] The present invention relates to the technical field of request processing, in particular, to a request processing method and a request processing device. Background technique [0002] The current system generally adopts data integration, and data integration is a relatively traditional system integration method, the center of which is data. For example, the trading system will operate the order table and the user table to generate orders. The SMS notification system will also access the order table and user table, and send different text messages to notify different users according to the status of the order: for example, send some promotional text messages to users corresponding to large orders, and send some promotional text messages to users who have not completed orders. The user sends a text message to remind him to complete the order. This is a data integration method, but both the transaction system and the SMS notification system rely on the...

AI Technical Summary

Problems solved by technology

[0004] Poor security: Each system exposes the interface in the form of HTTP (Hyper Text Transfer Protocol, Hypertext Transfer Protocol), and the security of the interface is poor;

[0005] Scalability problem: If the transaction system wants to move the order table from the RDBMS (Relational Database Management System) in the future, it may not be so easy, because there are many other systems that also rely on the order table, which can be said to affect the whole body; Or each system may add or delete fields to the table without authorization, which will bring bad consequences;

[0007] In short, the existing data integration code is complex, difficult to understand, and difficult for newcomers to get started; difficult to maintain, many people need to maintain, high team management costs, and lower team efficiency; system startup is generally slow; continuous deployment is difficult: every A small change requires re-deployment of the entire application; fixed technology stack: the cost of trying new technologies is too high; difficult expansion: some parts of the application are IO-intensive and some parts are CPU-intensive, but the application is only deployed in one On a single machine, it is difficult to use a single piece of hardware to meet the different requirements for hardware resources of each part of the application

Images