CN109857801B - Intelligent irrigation area e platform based on four-layer architecture and data processing method - Google Patents
Intelligent irrigation area e platform based on four-layer architecture and data processing method Download PDFInfo
- Publication number
- CN109857801B CN109857801B CN201910286658.6A CN201910286658A CN109857801B CN 109857801 B CN109857801 B CN 109857801B CN 201910286658 A CN201910286658 A CN 201910286658A CN 109857801 B CN109857801 B CN 109857801B
- Authority
- CN
- China
- Prior art keywords
- layer
- request
- service
- data
- application
- 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.)
- Active
Links
Images
Abstract
Compared with the traditional three-layer architecture, the intelligent irrigation area e platform based on the four-layer architecture and the data processing method thereof have the advantages that a routing layer is added between the original application layer and the service layer, the front-end application and the back-end data processing service are physically isolated, the tightness of the logical relation between the front end and the back end is reduced, and the expandability of a program is improved. The unified front-end development interface is applied in the application layer, so that the front-end page has the same layout, unified style, complete functional operation and related data, the development efficiency of the front-end application can be improved, the high unification of the front-end page can be effectively improved, and the front-end development is more standardized. The routing layer can also perform queue processing on the front-end application request and receive the back-end service response, so that the response and processing efficiency of the front-end application request are effectively improved, the platform has high concurrency processing, and a user can obtain better access experience.
Description
Technical Field
The invention belongs to the technical field of water conservancy informatization, and particularly relates to an intelligent irrigation area e platform method based on a four-layer architecture and a data processing method.
Background
At present, in the development of application systems, especially Web application systems, a traditional three-layer full-stack architecture mode is mostly adopted in the technical architecture design of the system, that is: presentation layer (UI), Business Logic Layer (BLL), Data Access Layer (DAL). The main technical advantages of the three-tier architecture can be summarized as follows:
1) the requirements on developers are low, and all development work from the front end to the back end can be completed only by learning and concentrating on a certain development language;
2) developers may be interested in only one layer of the overall structure;
3) the multiplexing of each layer of logic is facilitated;
4) the safety is high. The user side can only access the data layer through the logic layer, thereby reducing entry points and shielding a plurality of dangerous system functions;
5) the project structure is clearer, the labor division is more definite, and the later maintenance and the upgrading are facilitated.
While the three-tier architecture scheme has many advantages as described above, many problems and deficiencies are evident as the architecture scheme continues to be applied and further. Such as:
1) reducing the performance of the system. This is self-evident. If a hierarchical structure is not adopted, a plurality of businesses can directly visit the database to obtain corresponding data, and the corresponding data can be obtained through an intermediate layer.
2) Sometimes leading to cascade modifications. This modification is particularly embodied in a top-down direction. If a function needs to be added to the presentation layer, corresponding codes may need to be added to the corresponding service logic layer and data access layer to ensure that the design conforms to the hierarchical structure
3) The code amount and the workload are increased
Such as the above problems, the coupling degree of the front-end and back-end programs is strong, the system change and upgrade are difficult, the expandability is not strong, and the dynamic assembly of the module cannot be realized; the load balancing capability is weak, and large concurrent access cannot be processed; especially, today with the rapid development of internet and cloud technologies, such an architecture mode cannot meet the requirement of large centralized cloud deployment. Therefore, the software development method is more suitable for the development trend of software development technologies such as the current internet, big data, cloud computing and the like, more meets the requirements of a platform and standard software product, and can meet the requirement of high-concurrency access and processing of a novel software technology architecture mode, namely, the mode of the 'four-layer architecture' is necessary and urgent to change.
Disclosure of Invention
In order to solve the technical problem, the invention provides an intelligent irrigation area e platform based on a four-layer architecture and a data processing method.
The specific technical scheme of the invention is as follows:
the invention provides an intelligent irrigation area e platform based on a four-layer framework, which comprises the following parts:
the application layer is used for receiving an enabling request sent by a user to any functional module in the system, calling a specified page according to the request, configuring a corresponding control to form an operation interface, and loading and displaying the configured operation interface;
the routing layer is used for acquiring the enabling request from the application layer, putting the enabling request into an event queue, processing the enabling request according to the sequence and responding a processing result to the application layer;
the service layer is used for receiving and responding to the service calling request and the data interaction request sent by the routing layer and carrying out data interaction with the data layer;
and the data layer is used for constructing a database to store all data of the front end and the back end and receiving and responding to the data interaction request.
Further, the application layer includes the following parts:
the page library is used for providing page templates of the operation pages for all the functional modules in the system and calling corresponding page templates according to requirements;
and the application container is used for providing a tool and a material for configuring the page template for the operation page, and configuring the page template by using the tool and the material to obtain the operation page.
Further, the application container comprises the following parts:
the style library is used for providing layout and style support for the operation interfaces of all the functional modules, and comprises the overall layout of a system platform, the layout of the functional modules, the style of a platform frame and the styles of all controls related in the functional modules, so that the normal display of the front-end application module is ensured;
the control library is used for providing accessories and tools for the operation interfaces of all the function modules;
the resource library is used for uniformly integrating and storing all the resources in the forms of graphs, diagrams, pictures and characters related to the system platform and definitely calling the resources;
the method library is used for uniformly classifying and packaging the public operation method related to the front end so as to be called when the function module realizes the function operation of the front end;
and the application space is used for providing a space for configuring and loading the operation interface.
Further, the routing layer includes the following parts:
the V8 engine is used for compiling the enabling request sent by the application layer into machine codes which can be executed by a CPU, sending the machine codes to an event driver for processing, and responding to the application layer after a processing result is decompiled;
the runtime is used for forwarding the machine code to an event driver for processing and returning the processing result to the V8 engine;
the event driver is used for putting the received machine code into an event queue, delivering the events in the event queue to a working thread in sequence, sending a service calling request and a data interaction request to the service layer and carrying out asynchronous calling; and returning the processing result to an event queue and returning the processing result to the V8 engine by the runtime.
Further, the method of the asynchronous call is as follows:
after the event driver program initiates an asynchronous request, packaging the request into a request object; setting parameters and callback functions for the request object, and putting the request object into a thread pool; checking whether an available thread exists in the thread pool, executing the I/O operation of the request object when the available thread exists, putting the execution completion result into the request object, and informing the port of call completion.
Further, the service layer includes the following parts:
the RESTFUL layer is used for receiving and responding to the service calling request and the data interaction request sent by the routing layer and transmitting the data interaction request related to the database to the DAO layer;
the DAO layer is used for processing the data interaction request and returning a processing result to the RESTFUL layer;
and the database access interface is used for connecting and accessing the data layer.
The invention provides a four-layer architecture-based intelligent irrigation area e platform data processing method, which is characterized by comprising the following steps of:
s1: the application layer receives an enabling request sent by a user to any functional module in the system and forwards the enabling request to the routing layer;
s2: the routing layer puts the enabling request into an event queue, processes the enabling request according to the sequence and sends a service calling request to a service layer according to the enabling request;
s3: the service layer receives a service calling request and a data interaction request sent by the routing layer, processes the service calling request and calls data from the data layer according to the data interaction request;
s4: the service layer returns the processing result to the routing layer and further responds to the application layer;
s5: and the application layer calls a specified page according to the processing result request, configures a corresponding control to form an operation interface, and loads and displays the configured operation interface.
Further, the specific method of step S2 is as follows:
s2.1: after receiving the enabling request, the routing layer compiles the enabling request into machine codes which can be executed by a CPU (central processing unit) through a V8 engine and sends the machine codes to an event driver for processing through running;
s2.2: and the event driving program puts the machine code into an event queue, delivers the events in the event queue to a working thread in sequence, and sends a service calling request to the service layer for asynchronous calling.
Further, the specific method of step S2.2 is as follows:
after the event driver program initiates an asynchronous request, packaging the request into a request object; setting parameters and callback functions for the request object, and putting the request object into a thread pool; checking whether an available thread exists in the thread pool, executing the I/O operation of the request object when the available thread exists, putting the execution completion result into the request object, and informing the port of call completion.
Further, the specific method of step S3 is as follows:
s3.1: the service layer receives a service calling request and a data interaction request sent by the routing layer through a RESTFUL layer, and transmits the data interaction request related to the database to a DAO layer;
s3.2: the RESTFUL layer processes the service calling request;
s3.3: and the DAO layer accesses the data layer through a database access interface, calls corresponding data from the data layer according to the data interaction request, and returns a processing result to the RESTFUL layer.
The invention has the following beneficial effects: compared with the traditional three-layer architecture, the intelligent irrigation area e platform based on the four-layer architecture and the data processing method have the advantages that the routing layer 2 is additionally arranged between the original expression layer (namely, the application layer 1) and the business logic layer (namely, the service layer 3), the front-end application and the back-end data processing service are physically isolated, the tightness of the logic relation between the front end and the back end is reduced, and the expandability of a program is improved; meanwhile, the system platform adds a function of being compatible with databases of different manufacturers in the data layer 4, so that the storage mode of the system platform for the data source becomes more flexible, and different requirements of different users are met. The unified front-end development interface is applied in the application layer 1, so that the front-end page has the same layout, unified style, complete functional operation and related data, the development efficiency of the front-end application can be improved, the high unification of the front-end page can be effectively improved, and the front-end development is more standardized. The introduction of the routing layer 2 greatly reduces the coupling degree of the front and back end programs, so that the expansibility of the platform is enhanced, and the individual requirements of users can be met and realized conveniently. Meanwhile, the routing layer 2 can also perform queue processing on the front-end application request and receive the back-end service response, so that the response and processing efficiency of the front-end application request are effectively improved, the request needing to be processed for a long time is processed in a segmented manner, and the request completed in a short time is processed in time, so that the platform has high-concurrency processing and a user obtains better access experience.
Drawings
Fig. 1 is a schematic structural diagram of an intelligent irrigation area e platform based on a four-layer architecture according to embodiment 1;
fig. 2 is a schematic structural diagram of an application layer in an intelligent irrigation area e platform based on a four-layer architecture according to embodiment 2;
fig. 3 is a schematic structural diagram of a routing layer in an intelligent irrigation area e platform based on a four-layer architecture according to embodiment 3;
fig. 4 is a schematic structural diagram of a service layer in an intelligent irrigation area e platform based on a four-layer architecture according to embodiment 4;
fig. 5 is a schematic overall structure diagram of an intelligent irrigation area e platform based on a four-layer architecture according to embodiment 4;
fig. 6 is a flowchart illustrating a data processing method for an intelligent irrigation area e-platform based on a four-layer architecture according to embodiment 5;
fig. 7 is a flowchart of step S2 in the method for processing data of an intelligent irrigation area e-platform based on a four-layer architecture according to embodiment 6;
fig. 8 is a flowchart of step S3 of the method for processing data of an intelligent irrigation area e-platform based on a four-layer architecture according to embodiment 7.
Detailed Description
The present invention will be described in further detail with reference to the following examples and drawings.
Example 1
As shown in fig. 1, an embodiment 1 of the present invention provides an intelligent irrigation area e platform based on a four-layer architecture, which includes the following parts:
the application layer 1 is used for receiving an enabling request sent by a user to any functional module in the system, calling a specified page according to the request, configuring a corresponding control to form an operation interface, and loading and displaying the configured operation interface;
the routing layer 2 is used for acquiring the enabling request from the application layer 1, putting the enabling request into the event queue, processing the enabling request according to the sequence and responding the processing result to the application layer 1;
the service layer 3 is used for receiving and responding to the service calling request and the data interaction request sent by the routing layer 2, and carrying out data interaction with the data layer 4;
and the data layer 4 is used for constructing a database to store all data of the front end and the back end, receiving and responding to data interaction requests, comprises an ORACLE data and SQL SERVER database, supports various relational databases by utilizing Mybatis, and is compatible with different operating systems and data of different formats.
Compared with the traditional three-layer architecture, the intelligent irrigation area e platform based on the four-layer architecture has the advantages that the routing layer 2 is additionally arranged between the original expression layer (namely, the application layer 1) and the business logic layer (namely, the service layer 3), the front-end application and the back-end data processing service are physically isolated, the tightness of the logic relation between the front end and the back end is reduced, and the expandability of a program is improved; meanwhile, the system platform adds a function of being compatible with databases of different manufacturers in the data layer 4, so that the storage mode of the system platform for the data source becomes more flexible, and different requirements of different users are met. The unified front-end development interface is applied in the application layer 1, so that the front-end page has the same layout, unified style, complete functional operation and related data, the development efficiency of the front-end application can be improved, the high unification of the front-end page can be effectively improved, and the front-end development is more standardized. The introduction of the routing layer 2 physically separates the front end and the rear end of the whole platform, the front end can be more concentrated in functional application, the rear end is more biased to data processing, one is oriented to application, the other is oriented to service data, and the front end and the rear end respectively perform their own functions, so that the application effect and the processing efficiency of the front end and the rear end are greatly improved; due to the thorough separation of the front end and the back end, the coupling degree of the front end program and the back end program is greatly reduced, the expansibility of the platform is enhanced, and the individual requirements of users can be met and realized conveniently. Meanwhile, a front-end request processing queue program similar to a Windows operating system message queue is introduced and developed in the routing layer 2 for receiving and processing a front-end application request and receiving a back-end service response, so that the response and processing efficiency of the front-end application request are effectively improved, the request needing to be processed for a long time is processed in a segmented mode, the request completed in a short time is processed in time, the platform has high-concurrency processing, and a user can obtain better access experience.
Example 2
As shown in fig. 2, embodiment 2 discloses a smart irrigation area e platform based on a four-layer architecture on the basis of embodiment 1, and this embodiment 2 further defines that the application layer (1) includes the following parts:
the page library 11 is used for providing page templates of operation pages for all functional modules in the system and calling corresponding page templates according to requirements;
and the application container 12 is used for providing tools and materials for configuring the page template for the operation page, and configuring the page template by using the tools and the materials to obtain the operation page.
The application container 12 comprises the following parts:
the style library 121 is used for providing layout and style support for the operation interfaces of all the functional modules, including the overall layout of the system platform, the layout of the functional modules, the style of the platform framework and the styles of all the controls related in the functional modules, so as to ensure the normal display of the front-end application module;
the control library 122 is used for providing accessories and tools for the operation interfaces of all the functional modules;
the accessories and tools comprise various tables, charts, menus, tool bars, buttons and text boxes used by all functional modules in the platform, tree-shaped menus (measuring point trees, water unit trees, management mechanism trees and the like) containing part of service functions and the like; the platform takes easy UI as a control basis and carries out secondary packaging on the basis of the easy UI so as to meet the requirement of service of the irrigation district on application function and effect, and adds attributes and methods suitable for platform application, so that all controls in the control library become the basis of service development of the irrigation district and are converted into special functional controls of an intelligent irrigation district e platform;
the resource library 123 is used for uniformly integrating all the resources in the forms of graphs, diagrams, pictures and characters related to the system platform, storing the resources at a position designated by the platform, and definitely calling the resources at the same time, so that the resource data of the platform can be uniformly managed easily;
the method library 124 is used for uniformly classifying and packaging public operation methods related to the front end, removing the particularity of each method and increasing the universality of the method, so that the front end function module can call the corresponding method when realizing the front end function operation, thereby improving the uniformity of the front end application of the whole platform;
the current method library 124 mainly includes public operation methods such as a water gauge production method, a picture amplification method, a mouse wheel rolling method, an automatic hidden menu method, a time axis generation method and the like;
and an application space 125 for providing a space for configuring and loading the operation interface.
When a user initiates a request to a certain function module in the system, the application layer 1 receives the user request, transmits the user request to the routing layer 2 and waits for the response of the routing layer 2; after receiving the response of the routing layer 2, the application layer 1 will call the specified page from the page library 11 to load into the application space 125 according to the response requirement; the style library 121, the control library 122, the resource library 123 and the method library 134 provide support for pages running in an application space, so as to ensure that the displayed styles are accurate, the control functions are available, the resources are displayed normally, and the method calls are error-free. And finally, displaying the interface requested by the user in a browser for the user to use.
Example 3
As shown in fig. 3, embodiment 3 discloses an intelligent irrigation area e platform based on a four-layer architecture based on embodiment 2, and this embodiment 3 further defines that the routing layer 2 includes the following parts:
the V8 engine 21 is configured to compile an enabling request sent by the application layer 1 into machine code that can be executed by the CPU, send the machine code to the event driver 23 for processing, and respond to the application layer 1 after decompiling a processing result;
the V8JavaScript engine is a bottom layer JavaScript engine used by Google for a Chrome browser of the Google and is used for improving the performance of JavaScript execution inside a web browser; for this purpose, the V8 engine converts JavaScript code into efficient machine code, rather than relying on an interpreter to execute. The V8 engine introduces JIT to convert JavaScript code to machine code at runtime; the main difference here is that the V8 engine does not generate bytecode or any intermediate code, but converts directly to machine code;
the runtime 22 is used for forwarding the machine code to the event driver 23 for processing and returning the processing result to the V8 engine 21;
adopting Nodejs as a runtime (runtime), executing a javascript code at a server side, compiling the request into a machine code which can be executed by a CPU by a V8 engine 21 after a routing layer 2 receives a request initiated by an application layer 1, and then delivering the compiled machine code to an event driver 3(LIBUV) of the Nodejs for execution by a binging program of the Nodejs;
the event driver 23 is configured to place the received machine code in an event queue, deliver events in the event queue to a worker thread in sequence, send a service call request and a data interaction request to the service layer 3, and perform asynchronous call; the processing results are returned to the event queue and returned by the runtime 22 to the V8 engine 21.
The principle of the event driver 23 is to put the received machine code into an event queue (event queue), and the executive program sequentially delivers the events in the event queue to the worker threads (worker threads) to asynchronously call the service layer 3, and returns the processing result to the event queue, and then the executive program returns the processing result in the event queue to the V8 engine 21, and finally the V8 engine 21 performs decompiling and then responds to the application layer 1.
The method of asynchronous calling is as follows:
after the event driver 23 initiates an asynchronous request, the request is encapsulated into a request object; setting parameters and callback functions for the request object, and putting the request object into a thread pool; checking whether an available thread exists in the thread pool, executing the I/O operation of the request object when the available thread exists, putting the execution completion result into the request object, and informing the port of call completion.
The main idea of the event driver 23 is to perform flow control of the application program through event or state change, generally completed through event monitoring, and once an event is detected, call a corresponding callback function; the event-driven main execution process is that when a new request comes in, the request is pushed into a queue, then a loop is used to detect the state change of the event in the queue, and if the event with the state change is detected, the processing code corresponding to the event is executed, generally called a callback function.
The thread driver is that when a request is received, a new thread is opened for the request to process the request. And threads are managed primarily by a thread pool. When the thread pool has idle threads, the threads are taken from the thread pool for processing, and if no idle threads exist in the thread pool, new requests enter a queue to be queued until the idle threads exist in the thread pool.
Example 4
As shown in fig. 4 to 5, embodiment 4 discloses an intelligent irrigation area e platform based on a four-layer architecture based on embodiment 3, and embodiment 4 further defines that the service layer 3 includes the following parts:
the RESTFUL layer 31 is used for receiving and responding to the service calling request and the data interaction request sent by the routing layer 2, and transmitting the data interaction request related to the database to the DAO layer 32;
the DAO layer 32 is configured to process the data interaction request and return a processing result to the RESTFUL layer 31;
a database access interface 33 for connecting to and accessing the data layer 4.
The service layer uses java as a main development technology, the RESTFUL layer 31 receives and corresponds to a routing layer request through a Jersey framework, program intercommunication between the RESTFUL layer 31 and the DAO layer 32 is realized through a Spring framework, and finally the DAO layer 42 realizes access to various relational databases through a database access interface 33 (JDBC). The Jersey framework is combined with the Spring framework by defining a set of standard interfaces, the Jersey is used for receiving a request sent by a front-end application, then a data interaction request needing to be completed through a database is transmitted to a DAO layer 32 of the Spring for processing through the standard interfaces (including a basic interface, a data format processing interface, a framework interface, a public query interface and a mobile terminal interface), and a processing result is returned to a Restful layer 31 of the Jersey in a Json mode, so that the data operation logic of a back-end service is realized.
Example 5
As shown in fig. 6, an embodiment 5 of the present invention provides a data processing method for an intelligent irrigation area e platform based on a four-layer architecture, including the following steps:
s1: the application layer 1 receives an enabling request sent by a user to any functional module in the system and forwards the enabling request to the routing layer 2;
s2: the routing layer 2 puts the enabling request into an event queue, processes the enabling request according to the sequence, and sends a service calling request to the service layer 3 according to the enabling request;
s3: the service layer 3 receives the service calling request and the data interaction request sent by the routing layer 2, processes the service calling request and calls data from the data layer 4 according to the data interaction request;
s4: the service layer 3 returns the processing result to the routing layer 2 and further responds to the application layer 1;
s5: and the application layer 1 calls a specified page according to the processing result request, configures a corresponding control to form an operation interface, and loads and displays the configured operation interface.
The embodiment provides an intelligent irrigation area e platform data analysis method based on a four-layer architecture, which is characterized in that information transfer between an application layer 1 and a service layer 3 is realized through a routing layer 2, front-end application and back-end data processing service are physically isolated, the tightness of the logical relationship between the front end and the back end is reduced, and the expandability of a program is improved; the front-end request processing queue program of the message queue is used for receiving and processing a front-end application request and receiving a back-end service response, so that the response and processing efficiency of the front-end application request are effectively improved, the request needing to be processed for a long time is processed in a segmented mode, the request completed in a short time is processed in time, high-concurrency data processing can be achieved, and the data analysis and processing efficiency is greatly improved.
Example 6
As shown in fig. 7, embodiment 6 discloses a data processing method for an intelligent irrigation e-platform based on a four-layer architecture based on embodiment 5, and embodiment 6 further defines the specific method of step S2 as follows:
s2.1: after receiving the enabling request, the routing layer 2 compiles the enabling request into machine code executable by the CPU through the V8 engine 21, and sends the machine code executable by the CPU to the event driver 23 for processing through the runtime 22;
s2.2: the event driver 23 puts the machine code into the event queue, delivers the events in the event queue to the worker thread in order, and sends a service call request to the service layer 3 to make an asynchronous call.
The specific method of step S2.2 is as follows:
after the event driver 23 initiates an asynchronous request, the request is encapsulated into a request object; setting parameters and callback functions for the request object, and putting the request object into a thread pool; checking whether an available thread exists in the thread pool, executing the I/O operation of the request object when the available thread exists, putting the execution completion result into the request object, and informing the port of call completion.
The method comprises the steps of performing flow control on an application program through event or state change, generally completing the process through event monitoring, and calling a corresponding callback function once an event is detected; when a new request is received, the request is pushed into a queue, then the state change of an event in the queue is detected through a cycle, and if the event with the state change is detected, a processing code corresponding to the event is executed, wherein the processing code is generally a callback function; the thread driver is that when a request is received, a new thread is opened for the request to process the request. And threads are managed primarily by a thread pool. When the thread pool has idle threads, the threads are taken from the thread pool for processing, and if no idle threads exist in the thread pool, new requests enter a queue to be queued until the idle threads exist in the thread pool.
Example 7
As shown in fig. 8, embodiment 7 discloses a data processing method for an intelligent irrigation e-platform based on a four-layer architecture based on embodiment 5, and embodiment 7 further defines the specific method of step S3 as follows:
s3.1: the service layer 3 receives the service call request and the data interaction request sent by the routing layer 2 through the RESTFUL layer 31, and transfers the data interaction request related to the database to the DAO layer 32;
s3.2: the restul layer 31 processes the service invocation request;
s3.3: the DAO layer 32 accesses the data layer 4 through the database access interface 33, retrieves corresponding data from the data layer 4 according to the data interaction request, and transmits the processing result back to the RESTFUL layer 31.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (6)
1. An intelligent irrigation area e platform based on a four-layer architecture is characterized by comprising the following parts:
the system comprises an application layer (1) and a function module, wherein the application layer is used for receiving an enabling request sent by a user to any function module in the system, calling a specified page according to the request, configuring a corresponding control to form an operation interface, and loading and displaying the configured operation interface;
the routing layer (2) is used for acquiring the enabling request from the application layer (1), putting the enabling request into an event queue, processing the enabling request according to the sequence and responding the processing result to the application layer (1);
the service layer (3) is used for receiving and responding to the service calling request and the data interaction request sent by the routing layer (2), and carrying out data interaction with the data layer (4);
the data layer (4) is used for constructing a database to store all data of the front end and the back end and receiving and responding to the data interaction request;
the routing layer (2) comprises the following parts:
a V8 engine (21) for compiling the enabling request sent by the application layer (1) into machine code executable by a CPU and sending the machine code to a runtime module (22);
a runtime module (22) for forwarding the machine code to an event driver (23) for processing, receiving a processing result of the event driver (23), and returning the processing result to the V8 engine (21);
the V8 engine (21) is further configured to: receiving the decompiling of the processing result returned by the runtime module (22) and then sending the decompiled processing result to the application layer (1);
the event driver (23) is used for putting the received machine code into an event queue, delivering the events in the event queue to a working thread in sequence, sending a service calling request and a data interaction request to the service layer (3) and carrying out asynchronous calling; returning the processing result to an event queue and sending to the runtime module (22);
the method for asynchronous calling comprises the following steps:
after the event driver (23) initiates an asynchronous request, packaging the request into a request object; setting parameters and callback functions for the request object, and putting the request object into a thread pool; checking whether an available thread exists in the thread pool, executing the I/O operation of the request object when the available thread exists, putting the execution completion result into the request object, and informing the port of call completion.
2. The smart irrigated area e platform based on the four-layer architecture of claim 1, wherein the application layer (1) comprises the following parts:
the page library (11) is used for providing page templates of operation pages for all functional modules in the system and calling corresponding page templates according to requirements;
and the application container (12) is used for providing tools and materials for configuring the page template for the operation page, and configuring the page template by using the tools and the materials to obtain the operation page.
3. The smart irrigated area e platform based on a four-tier architecture as claimed in claim 2, wherein the application container (12) comprises the following parts:
the style library (121) is used for providing layout and style support for the operation interfaces of all the functional modules, and comprises the overall layout of a system platform, the layout of the functional modules, the style of a platform frame and the styles of all controls related in the functional modules, so that the normal display of the front-end application module is ensured;
the control library (122) is used for providing accessories and tools for the operation interfaces of all the function modules;
the resource library (123) is used for uniformly integrating and storing all the resources in the forms of graphs, diagrams, pictures and characters related to the system platform and definitely calling the resources; the method library (124) is used for uniformly classifying and packaging the public operation methods related to the front end so that the functional modules can be called when the front-end functional operation is realized;
and the application space (125) is used for providing a space for configuring and loading the operation interface.
4. The intelligent irrigation e-platform based on a four-layer architecture as claimed in claim 1, wherein the service layer (3) comprises the following parts:
a RESTFUL layer (31) for receiving and responding to the service calling request and the data interaction request sent by the routing layer (2), and transmitting the data interaction request related to the database to a DAO layer (32);
a DAO layer (32) for processing the data interaction request and returning the processing result to the RESTFUL layer (31);
a database access interface (33) for connecting to and accessing the data layer (4).
5. A four-layer architecture-based intelligent irrigation area e platform data processing method is characterized by comprising the following steps:
s1: the application layer (1) receives an enabling request sent by a user to any functional module in the system and forwards the enabling request to the routing layer (2);
s2: the routing layer (2) puts the enabling request into an event queue, processes the enabling request according to the sequence, and sends a service calling request to a service layer (3) according to the enabling request;
the specific method of step S2 is as follows:
s2.1: after receiving the enabling request, the routing layer (2) compiles the enabling request into machine codes which can be executed by a CPU through a V8 engine (21) and sends the machine codes to an event driver (23) for processing through a runtime module (22);
s2.2: the event driver (23) puts the machine code into an event queue, delivers the events in the event queue to a working thread in sequence, and sends a service calling request to the service layer (3) for asynchronous calling;
s3: the service layer (3) receives a service calling request and a data interaction request sent by the routing layer (2), processes the service calling request, and calls data from the data layer (4) according to the data interaction request;
s4: the service layer (3) returns the processing result to the event queue, and then the processing result is returned to the V8 engine (21) by the runtime module (22), and further responded to the application layer (1) by the V8 engine (21);
s5: the application layer (1) calls a specified page according to the processing result request, configures a corresponding control to form an operation interface, and loads and displays the configured operation interface;
the method for asynchronous calling comprises the following steps:
after the event driver (23) initiates an asynchronous request, packaging the request into a request object; setting parameters and callback functions for the request object, and putting the request object into a thread pool; checking whether an available thread exists in the thread pool, executing the I/O operation of the request object when the available thread exists, putting the execution completion result into the request object, and informing the port of call completion.
6. The method according to claim 5, wherein the step S3 is as follows:
s3.1: the service layer (3) receives the service calling request and the data interaction request sent by the routing layer (2) through a RESTFUL layer (31), and transmits the data interaction request related to the database to a DAO layer (32);
s3.2: the RESTFUL layer (31) processes the service invocation request;
s3.3: the DAO layer (32) accesses the data layer (4) through a database access interface (33), calls corresponding data from the data layer (4) according to the data interaction request, and returns a processing result to the RESTFUL layer (31).
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910002385 | 2019-01-02 | ||
| CN2019100023858 | 2019-01-02 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109857801A CN109857801A (en) | 2019-06-07 |
| CN109857801B true CN109857801B (en) | 2021-01-15 |
Family
ID=66903710
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910286658.6A Active CN109857801B (en) | 2019-01-02 | 2019-04-10 | Intelligent irrigation area e platform based on four-layer architecture and data processing method |
Country Status (2)
| Country | Link |
|---|---|
| JP (1) | JP2020109613A (en) |
| CN (1) | CN109857801B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111324395B (en) * | 2020-02-07 | 2023-11-03 | 京东科技控股股份有限公司 | Calling method, device and computer readable storage medium |
| CN112700225A (en) * | 2021-01-07 | 2021-04-23 | 湖南联智科技股份有限公司 | Technical architecture for unmanned aerial vehicle cruise monitoring platform management |
| CN112862628A (en) * | 2021-01-15 | 2021-05-28 | 哈尔滨鸿德亦泰数码科技有限责任公司 | Visual comprehensive display application platform for irrigation area |
| CN112860825A (en) * | 2021-01-15 | 2021-05-28 | 哈尔滨鸿德亦泰数码科技有限责任公司 | Method and system for realizing one map of irrigation area management |
| CN112860225A (en) * | 2021-01-15 | 2021-05-28 | 哈尔滨鸿德亦泰数码科技有限责任公司 | Intelligent irrigation area e platform with excellent expandability and secondary development structure construction method thereof |
| CN113206873A (en) * | 2021-04-22 | 2021-08-03 | 哈尔滨鸿德亦泰数码科技有限责任公司 | Method for constructing intelligent irrigation area e platform routing layer by node |
| CN114379454B (en) * | 2022-01-29 | 2024-03-22 | 重庆长安汽车股份有限公司 | Turning light function service system based on SOA architecture |
| CN115033282B (en) * | 2022-06-30 | 2023-08-22 | 杭州凯达电力建设有限公司 | Charging pile operation platform compatible method, device, equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107483533A (en) * | 2017-06-28 | 2017-12-15 | 麦可思数据（北京）有限公司 | A kind of intelligent assiatant's system |
| CN108319506A (en) * | 2017-01-17 | 2018-07-24 | 贵州白山云科技有限公司 | A kind of data hierarchy processing method and processing device |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3911397B2 (en) * | 2000-08-09 | 2007-05-09 | 富士通株式会社 | Program development support apparatus, program development support method, medium, and program |
| CN103123593B (en) * | 2011-11-18 | 2016-08-31 | 腾讯科技（深圳）有限公司 | Java application server and the method processing Web service |
| CN104484182A (en) * | 2014-12-25 | 2015-04-01 | 广东电子工业研究院有限公司 | Elastic extensible multi-data-source mvc (model-view-controller) model architecture |
| CN107111497A (en) * | 2015-01-16 | 2017-08-29 | 株式会社野村综合研究所 | Development support system |
| CN106325703B (en) * | 2015-07-03 | 2019-07-19 | 宁波弘讯科技股份有限公司 | Webpage human-computer interface control equipment and its operation method |
| CN105843609A (en) * | 2016-03-18 | 2016-08-10 | 浪潮软件集团有限公司 | MVC frame based on Spring and MyBatis |
| CN106130759B (en) * | 2016-06-22 | 2021-02-09 | 白杨 | Service-oriented modular system architecture |
-
2019
- 2019-04-10 CN CN201910286658.6A patent/CN109857801B/en active Active
- 2019-09-02 JP JP2019159258A patent/JP2020109613A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108319506A (en) * | 2017-01-17 | 2018-07-24 | 贵州白山云科技有限公司 | A kind of data hierarchy processing method and processing device |
| CN107483533A (en) * | 2017-06-28 | 2017-12-15 | 麦可思数据（北京）有限公司 | A kind of intelligent assiatant's system |
Non-Patent Citations (4)
| Title |
|---|
| 三：事件驱动以及循环;谢玉胜;《https://www.jianshu.com/p/b6b219455b8c》;20180608;第1页第1行-第2页第6行6行 * |
| 在表现层和逻辑层之间增加服务层，是为了什么？;amandag;《https://zhidao.baidu.com/question/297831180.html》;20171124;第1页第1行-第1页最后一行 * |
| 基于页面容器的Web 应用框架;程文青等;《计算机工程》;20080229;第34卷(第3期);第283页左栏第14行-第285页右栏最后一行 * |
| 用于构建 RESTful Web 服务的多层架构;Bruce Sun;《https://www.ibm.com/developerworks/cn/web/wa-aj-multitier/index.html》;20090803;第3页第14行-第4页最后一行 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109857801A (en) | 2019-06-07 |
| JP2020109613A (en) | 2020-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109857801B (en) | Intelligent irrigation area e platform based on four-layer architecture and data processing method | |
| US8307015B2 (en) | Decorated model architecture for efficient model-driven application development | |
| US8209710B2 (en) | Implementation system for business applications | |
| US9110686B2 (en) | Web client command infrastructure integration into a rich client application | |
| CN102375731A (en) | Coding-free integrated application platform system | |
| WO2020238597A1 (en) | Hadoop-based data updating method, device, system and medium | |
| CN113504902B (en) | Industrial APP integrated development system and related equipment | |
| CN106990970B (en) | MVC-based dynamic page generation method and system | |
| CN106951254B (en) | Method and device for multiplexing similar service function modules in payment system | |
| US10509632B2 (en) | Model augmentation in a model-driven application development environment | |
| WO2023124543A1 (en) | Data processing method and data processing apparatus for big data | |
| CN109542425B (en) | Automatic application method and system of retail supply chain | |
| CN113934832A (en) | Interactive processing method, device, equipment, medium and program product based on session | |
| CN107153679B (en) | Extraction statistical method and system for semi-structured big data | |
| CN116909553A (en) | Page online development and local compiling operation system | |
| CN115509531A (en) | Micro front end implementation method, device, terminal and storage medium based on front end technology | |
| CN111381811A (en) | Software resource integration platform suitable for integration of multiple types of information systems | |
| CN115145652A (en) | Method, device, equipment and medium for creating data processing task | |
| CN116186022A (en) | Form processing method, form processing device, distributed form system and computer storage medium | |
| CN109271143B (en) | Micro-service architecture based on cloud service | |
| CN109597611A (en) | Front end data flow control Components Development system, method, equipment and storage medium | |
| CN114048196B (en) | Workflow system data processing method, device, equipment and storage medium | |
| CN110908641B (en) | Visualization-based stream computing platform, method, device and storage medium | |
| CN114942768A (en) | Cross-platform operation method and device | |
| Betzing | Design and Development of an Event-driven In-memory Business Process Engine |
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 |