1. The traditional three-tier architecture
FIG MVC is based with a three-tier architecture, it can be divided into the presentation layer, the business layer and persistence layer
The presentation layer is responsible for receiving the request and forwards the request
The business layer processes the request, is worth noting that transaction management, logging, and other operations are typically encapsulated in this layer
Persistence layer is responsible for operations between the database and the entity
We can use the framework to simplify the development of the layers, such as the presentation layer using SpringMVC or Strut2, persistence layer using Mybatis or Hibernate, using the relationship between the three-Spring management
2. cluster architecture
Clusters belong to the level of development.
There are many problems in the conventional three-tier architecture, such as the business layer in the proportion of the different modules of the system resources that much difference, leading to system resources, you can use the cluster to solve such problems.
In a cluster architecture, generally composed of such an important role, and that is a reverse proxy server, its main task is to achieve load balancing, the receiving user requests, forwarded to the target server.
Nginx reverse proxy server can be used to achieve.
3. Distributed Architecture
The plurality of modules perform one function.
Each module can build a cluster -> High Availability
4. Micro Services Architecture
The product service function module divides the type of service, which is a vertical division.
The client can be called micro-services-based HTTP or RPC way, the aim is to reduce the performance overhead of calls generated.
Each module can also be set up clusters -> High Availability
Three kinds of lightweight API call to service - service register and use the service gateway calls between client and service implementations micro (communicate)
SOA communication between two systems in three ways
dubbo architecture: