An application can be developed with an amazing architecture, using the latest technologies and having the best interface, etc. but if it doesn’t solve the business’s needs, it won’t be considered useful for it. That’s when domain driven design (DDD) comes in. As its name says, the point here is to focus on the domain of a specific business.
In fact, to design a good software, it’s important to know what that software is about. To create a banking software system, you need to have a good understanding of what banking is all about, one must understand the domain of banking.
In software development, the domain driven design approach is used for complex needs, connecting the implementation to an evolving model of the core business concepts. It puts the focus on the problem domain and basically helps identify the architecture and inform about the mechanics that the software needs to replicate.
DDD has a strategic value and it’s about mapping business domain concepts into software artifacts. It’s about organizing code artifacts in alignment with business problems, using the same common, ubiquitous language.
DDD isn’t a methodology, it’s more about the software’s architectural design, providing a structure of practices to take design decisions that help in software projects that have complicated domains.
The DDD approach was introduced by Eric Evans in the book Domain-Driven Design: Tackling Complexity in the Heart of Software. Each developer here at Apiumhub has read it and definitely recommend you to read it!
Mainly, domain driven design focuses on:
The core domain and domain logic
Complex designs on models of the domain
Improving the application model and resolving emerging domain-related issues by collaborating with domain experts
DDD encompasses a common language, techniques and patterns as well as an architecture. The focus is put on the business and on modelling the problems that are trying to be solved.
With DDD, the developers get techniques that will help minimizing the complexity and that will help driving collaboration with the rest. The idea is to use the requirements and to map out the business processes into the model by using the same language that is used by the business itself.
Here we talk about a language that is used by all the team in order to connect all the activities of the team with the software. The ubiquitous language of DDD helps when it comes to knowing more about terms that are used by the business experts. The tech team is able to know if the language changes and if a specific term will be used for a different meaning.
The context is a setting that determines the meaning of a statement.
A graph that connects the contexts together. For each context you find: a language, an independent implementation and an interface to talk to other bounded contexts.
The Bounded context is the context in which the Ubiquitous language and the corresponding models are valid. It gives the team a clear understanding of what has to be consistent and what can develop independently.
The model is a system that describes the selected aspects of a domain and that is often used to solve problems that are related to that particular domain.
With the business’ model, strategies and processes.
From other domains & layers in the business
With no dependencies on the layers of the application on either side of domain layer
To avoid models that are duplicated
To have a maintenance, testing, and versioning that is easier.
To avoid outliving those frameworks and getting tight coupling on external frameworks
Without having any technology or framework dependencies
We do agree that this is a very brief and short introduction to DDD. The point of this article was to have an idea of what is domain driven design. I will leave you with a list of key benefits of DDD that might make you even more curious about the topic!
As you know, with domain driven design, everyone ends up using the same language & terms and the team is sharing a model. Developers communicate better with the business team and the work is more efficient when it comes to establishing solutions for the models that reflect how the business operates, instead of how the software operates.
This is quite clear but let’s mention it again. Teams find communication much easier during the development cycle because from the beginning, they focus on establishing the ubiquitous language that is common to both parties (development & business experts). The language is linked to the domain model of the project and technical aspect are referred to through simples terms that all understand.
This goes without saying, if everyone is using the same terminology, it becomes quite simple to keep track of requirement implementation.
With DDD you end up with a more readable code and less duplication.
By following an agile approach that is iterative and incremental, DDD clarifies the mental model of domain experts into a useful model for the business.
Due to well understood bounced context, all the teams are able to understand where certain integrations are important and especially why. This means you know you’re getting a good software architecture.
Generally speaking, DDD comes in quite helpful when it comes to helping the team creating a common model. The teams from the business’ side and from the developer’s side can then use this model to communicate about the business requirements, the data entities, and process models.
With DDD you build around the concepts of the domain and around what the domain experts are advising. This implies that the applications developed will indeed represent what the domain needs instead of getting an application that is only focused on UX & UI, forgetting the rest of requirements. The most important is to get a balanced product that suits well the users/audience of that specific domain.
The fact that there are clean boundaries around pure models enables the developers to put their efforts on what matters the most, it enables them to focus on the solution.
DDD turns around the concepts of object-oriented design. This implies that almost everything in the domain model is based on an object and therefore will be modular and encapsulated, enabling the system to be changed and improved regularly and continuously.
The post An introduction to domain driven design & its benefits appeared first on Apiumhub.
This post was originally published on apiumhub.com