Clean Architecture & DDD, a mixed approach

At my current work at peya-tech we’ve been using a combined forces architecture for the last 6 months that has worked quite well so far. It consists of a mixture between the concepts of Clean Architecture and Domain Driven Design.

You can find plenty of information of both concepts around, there are great books explaining these topics and other sources. We’ll leave you some sources at the end of this article.

To set us in motion, The Clean Architecture first introduced by Robert C. Martin (aka Uncle Bob) defines an architecture for your software project that separates each layer according to clear different responsibilities. Moreover, Uncle Bob’s concept defines that information flow should follow always the same direction, from the outer to inner layers and back again.

This architecture relies heavily on some widely-known principles, the SOLID Principles, which I recommend you to have a look at.

Our co-star Domain Driven Design, commonly known as DDD, was first introduced by Eric Evans on the book by the same name. What Evans talks about in his book, heavily summarised, is that your software’s model should be really close to your business domain.

Between product and engineering you should talk a ubiquitous language when referring to concepts and that language should be…