Is the following separation considered a two-tier or three-tier architecture?

I have a web application that deploys as follows on a web host:

  • The code (without separating BLL, DAL, etc.) is uploaded to the web hosting.
  • The database (MSSQL backup file) is uploaded to the web hosting database

Is this a two-tier architecture or a three-tier architecture?

I saw different explanations from different sources

  • If the code and the database are on the same server, then it is 2-level. If the code and the database are on different servers, then this is a 3-level.
  • A database web application has a minimum 3-tier architecture.
  • This is a two-tier architecture.

Definition of the 2nd level by this source
In a two-tier architecture, the web server responds to requests for web pages, and the database server provides data storage on the backend.
Definition of a tiered source
In a three-tier architecture, the web server is associated with a middle level, which usually includes itself a number of application servers that perform specific tasks, as well as for the internal level of existing enterprise systems.

Hope someone can clarify this.

+4
source share
1 answer

It really depends on what you mean by the term “levels” in your question.

/ - 3 :

  • Client (browser) <--> Application Server <--> Database

, 2- :

  • Client <--> Database

, - 3 - , , .

- , , - , MVC, , , , , , , .

, , ( ), , , , , .

. , .

: , , .

+1

All Articles