After writing to find yourself as if many do not know, tube it, as long as their own understanding on the line, and later have time to improve this
The feeling is the three-layer architecture over and over, with this as the basis for continuous expansion, if the amount of data must be large, otherwise these extensions have no meaning
This is a very small amount of data structure (it seems that the previous static site is the same structure it)
The view layer + business Layer + persistence layer is included in the stored procedure
----
In fact, the database here can not be to this one, can do database chain
This is a large amount of data structure, and the page data is dynamic, that is, after loading the page once, but some hidden features require the user to manually trigger, but this time if re-refresh the page is certainly unrealistic, there is a dynamic load this concept, the front end is actually in the user triggered the event and then send a request query back to the background
Use interceptors to intercept all or specific requests at the view level, request distribution using a third-party plug-in package, distribute to the action code specified in the path, call the business layer code, and then call the persistence layer
------
Business layer optimization seems unclear, and sure enough, drawing is one of the best ways to understand your knowledge.
Another is in the structure above the data to peel off, because the above structure in the face of large data is very difficult, although can be solved with the database chain, but the feeling is too miscellaneous
The solution is to use multiple databases, but each database stores only one type of data, which stores data of a data type and can also create a database chain
Understanding of Java Web Development