architecture - What are changes in the application would create a new tier? -


About all its N-Tier architecture I had to use JSON in one page in my web application. That's why I called a tier as a DTO. So my question is right or wrong, what are the changes that will introduce more levels to an application.

  • Presentation / UI layer - Web page markup, styling e.t.c.
  • Business Logic Level (BLL) - 1 or more middle level that includes your application / business rules and functions
  • Data Access Layer (DAL) - level which relates to continuous Use of storage, such as unit structure, LINQ, etc.
  • Persistency Layer - The actual data layer, usually a database.

The development-of-development with N is that each layer plays an important role. It depends on the functionality of the underlying levels and does not know anything in the range above it. For example, you can have methods like DAL, Sevusur, Getuusser, etc. The Business Layer knows about these methods, but do not know about their implementation or do not even care about their implementation. Everyone knows that when the user needs to save or receive, he calls those methods.

The advantage of this is that you can change your database type from MySQL for example MSSQL, and only update your DAL, the layers given above do not know about it or about it Nobody cares.

How open your question is open, on this topic you may want to have a more background conversation on this subject, such as:


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -