Business logic layer key classification ()

The core of the application system should be the business logic layer.
It can also be classified as follows:
1. lifecycle control and container. In addition to controlling the lifecycle of components at the business layer. You can also control the lifecycle of other modules, or control the module-level lifecycle control containers in other modules. (Lifecycle control in the EJB standard in the application server. P.s. can at least be divided into two categories: application level and session level)
2. Business logic. The entity logical unit required to complete the required business. (Session Bean in EJB)
3. Business process logic. Determine the process relationship between business logic units based on the business process. (Workflow)

When the system is not large, the business layer itself is divided into other modules. For example, the struts controller can undertake the "Business process logic" capability.
In small web systems, you can often use web built-in lifecycle containers such as application session to perform lifecycle control.
In a large system, for example, an application server system may hand over lifecycle management to server management.

The current system is in China. Generally, the application server level is not reached, and most of them only use web servers. Therefore, more common systems use a range object such as appliction session to act as "lifecycle control and container ".

Therefore, the general system framework can well abstract and accept the "business logic"
Session data to greatly improve the development efficiency. However, if you want to do well, either use EJB and the application server, or write at least one session-level
Lifecycle control container (spring can be used for application-level management ).