Technical framework system based on distributed large website development

Abstract

The invention discloses a technical framework system based on distributed large website development. The technical framework system based on the distributed large website development comprises a single entry, a routing layer module, an input validation module, a form validation processing module, a control layer module, a model layer module, a presentation layer module, a unified resource module, a caching module, a data layer module and a data safety validation module, wherein the single entry, the routing layer module, the control layer module, the input validation module and the form validation processing module are sequentially connected, the input validation module and the form validation processing module are organically combined to form a whole, the whole is connected with the unified resource module, the presentation layer module and the model layer module, the unified source module, the presentation layer module and the model layer module are sequentially connected, the model layer module is connected with the data safety validation module, and the data safety validation module is connected with the caching module and the data layer module. A technology platform which is efficient, stable and high in expansibility is provided, and application requirements under the large load and the large number can be met.

Description

technical field [0001] The invention relates to a technical frame system based on distributed large-scale website development. Background technique [0002] At present, many websites need to process more and more requests, more and more data, and continuously add new functions according to operational needs. Many website systems often stop services due to insufficient framework design. . [0003] At present, domestic and foreign framework design is still based on the traditional programming idea of ​​database as the core. When the amount of data and visits are too large, the above problems will occur. Therefore, it is necessary to separate the database from the core of data storage and basic system services. Solve the pressure of the database, otherwise the bottleneck of the database is the bottleneck of the entire system, because the performance bottleneck of the database is very low, it will seriously restrict the performance of the system. Caching is the best way to sol...

AI Technical Summary

Problems solved by technology

[0009] 1) TinkPHP does not consider distributed systems enough: currently, for Internet interactive applications, distributed deployment is required in the case of a large number of visits. ThinkPHP exposes the problem of insufficient pressure-bearing capacity during the application process. Based on ThinkPHP, some products are developed in big data. It also needs to be refactored in the case of large volume and high traffic volume

[0010] 2) ThinkPHP does not handle the system core bottleneck database pressure enough: ThinkPHP still directly operates on the database in the process of processing data, and there is no effective caching mechanism

[0011] 3) ThinkPHP's caching function is too primitive: ThinkPHP provides some basic class libraries for caching processing, and realizes some basic functions. It has not yet integrated the caching processing mechanism into the data processing process, and the realization of caching functions requires self-programming.

[0012] 4) ThinkPHP lacks a data security verification mechanism: the biggest security problem in databases at present is SQL injection. Without a strict data security verification mechanism, there is no guarantee for system security

ThinkPHP has recently encountered a very serious security problem that can execute arbitrary code, which also exposes ThinkPHP's neglect of the security system during the design process

[0013] 5) ThinkPHP does not optimize the efficiency of program execution in the process of processing: for example, the core code of the template is matched with regular expressions, which is inefficient, and some professional templates almost do not use regular matches.

[0014] 6) ThinkPHP does not consider enough about the rapid development of programs and future scalability: ThinkPHP's support for read-write separation and sub-database sub-table is also relatively weak

[0015] 7) The openness of ThinkPHP is poor. The ability to introduce mature third parties is weak: Although there is a maturely developed Smarty template engine, it is useless. The built-in template engine implemented by itself is not only weak in function but also low in execution efficiency, and it is relatively expensive for developers to learn. high

[0025] 1) ZendFrameWork does not handle the system core bottleneck database pressure enough: ZendFrameWork still directly operates on the database in the process of processing data, and there is no effective caching mechanism

[0026] 2) The cache function of ZendFrameWork cannot effectively reduce the pressure on the database: ZendFrameWork provides some basic class libraries for cache processing and realizes some basic functions. programming

[0027] 3) The MVC function of ZendFrameWork is relatively weak, and the View layer is simply implemented (same as not implemented), and the front-end page cannot be well controlled

[0028] 4) The execution efficiency of ZendFramework is low: ZendFramework is a comprehensive and huge framework, and its application scenarios are more suitable for the application of complex relationship management and complex data management, so the execution efficiency of the program is relatively low

Images