CODEWITHSUNDEEP
.netnaming-conventionsn-tier-architecture
mflair2000
mflair2000

Reputation: 315

N-Tier Architecture Layer Naming Suggestions

I am looking to reorganize my backend n-tier application to break up the layers so that they are more independent and testable. I will have the following layers.

 Entities
 Data Access Layer
 Business Logic
 Contracts
 Service

Is there any best practices for naming these layers?

Upvotes: 0

Views: 793

Answers (1)

Declan
Declan

Reputation: 1860

Of course this is a matter of preference, but i would go with something like:

  • CompanyName.ApplicationName.Data
  • CompanyName.ApplicationName.Data.DataAccess
  • CompanyName.ApplicationName.BusinessLayer
  • CompanyName.Common.Contracts
  • CompanyName.Common.Services

Using "Common" where the library will be shared, and "ApplicationName", where they are specific to a single application.

Upvotes: 1

Related Questions