The Infrastructure Layer
The Infrastructure Layer is made up of all the technical details of how our application is implemented.
For example, most applications require a database and so the code that interacts with the database would sit in the Infrastructure Layer.
Domain Driven applications should rely on interfaces and not implementations. This means we would rely on a Mailer interface, but we would use a MailGunMailer implementation that implements the interface we require.
So far we’ve covered the following sections of the Infrastructure layer:
Creating a Mailer Infrastructure Service
Creating and testing Doctrine Repositories
The Infrastructure Layer is made up of all the technical details of how our application is implemented.
For example, most applications require a database and so the code that interacts with the database would sit in the Infrastructure Layer.
Domain Driven applications should rely on interfaces and not implementations. This means we would rely on a Mailer interface, but we would use a MailGunMailer implementation that implements the interface we require.
So far we’ve covered the following sections of the Infrastructure layer:
Creating a Mailer Infrastructure Service
Creating and testing Doctrine Repositories
No comments:
Post a Comment