Home  >  Article  >  Backend Development  >  Summarize the points to note about the three-tier framework

Summarize the points to note about the three-tier framework

巴扎黑
巴扎黑Original
2017-06-11 14:04:441224browse

Briefly describing the enterprise-level project, I never thought about the huge framework at the beginning, because the pressure at the beginning was not very high. Therefore, scalability has become a core requirement. Traditional three-tier architecture. Application layer, business logic layer, and data persistence layer. In view of the need to separate the server to reduce the pressure on the server, it is divided into a Web server, a business server, and a database server; and the reasonable and smooth data logic calls between the three, especially the front-end and back-end, are the key points that I need to record. Web front-end application service, requests the API interface, obtains data and renders the page. 1. Build an MVC framework and introduce public Model and interface calling class libraries. 2. Use the bootstrap framework to build a mobile-first front-end page framework. 3. According to business needs, call the backend interface and render the page. Web Api (logical service) is built to provide a stateless interface based on HTTP to handle interactive requests on the web side. The key aspects are as follows: 1. Under the premise that the interface is stateless, determine the permission level and corresponding legality of the request. (Rewrite the Http request, add the legality judgment of the request, and AOP-like aspect judgment) 2. Provide or rely on a unified data model for smooth interaction between the front and back ends. (Entity

1. Asp.net (1) Basic three-tier framework project: Web server, business server, database server

Summarize the points to note about the three-tier framework

Introduction: Briefly describe the enterprise-level project. I didn’t think about the huge framework at the beginning, because the pressure at the beginning was not very high, so the scalability. It has become a core requirement. The traditional three-tier architecture: application layer, business logic layer, and data persistence layer. In view of the need to separate servers to reduce server pressure, they are divided into Web servers, business servers, and database servers; especially among these three. Reasonable and smooth data logic calls on the front and back ends are the key points I need to record. Web front-end application services, requesting API interfaces, and obtaining data rendering pages. 1. Build an MVC framework and introduce public M...

2. Three-layer framework problem, please solve it! _html/css_WEB-ITnose

#Introduction: Three-layer framework problem, please solve it!

#【Related Q&A recommendations】:

The above is the detailed content of Summarize the points to note about the three-tier framework. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn