Theoretically, in general: Data access layer holds database connections and queries. Business layer holds the model and the logics. Service layer holds the main services the application services. Presentation layer holds the website. Am I right? did I miss something? What is the infrastructure layer?

Reputation: 24093

application layers

Theoretically, in general:

Data access layer holds database connections and queries.
Business layer holds the model and the logics.
Service layer holds the main services the application services.
Presentation layer holds the website.
1. Am I right? did I miss something?
2. What is the infrastructure layer?

Upvotes: 1

Reputation: 8295

Yes, I'd say you've described the layers correctly.

In my mind infrastructure can represent two things:

Cross cutting concerns - things like logging/auditing, authentication/security etc. I prefer to use Aspect oriented programming to deal with these types of things.
Third party systems/components/libraries that your application makes use of, such as a credit card payment gateway for example. Even the database platform you have chosen could be considered infrastructure.

Upvotes: 2

Reputation: 7148

The infrastructure layer tends to turn up in DDD and MVVM type projects. There's a simple diagram and quick explanation of the layers in DDD here.

It's based on a Java implementation, but the descriptions still hold up apart from the odd bit of Java terminology.

Upvotes: 0