The history of computing is a domain all unto it’s own. The context of this evolution is worth highlighting by first zooming out to the inventions that came before DDD. Then looking to programming as a field of experiments and inventions, we can consider DDD in light of those preceding inventions. This can help us form a deeper understanding of where the future of DDD and software is headed.
Domain-Driven Design (DDD) is not nearing the end of its life, it has just begun to materialize into a respected discipline. One evidence of this is the considerable growth of adoption in Europe and the amount of content, pro and con, related to DDD. These type of cultural advancements can take decades or, in the case of Babbage at the start of the timeline above, a century or more to reach much of their potential. Domain Driven Design United States is here to assist with this future along side all of the practitioners and enthusiasts working to help heal the software industry of less efficient and non-existent design practices that lead to software struggles. Both at the strategic and tactical level, we envision a world that finally dispenses with the natural tendency to assume domain experts need not be involved and somehow design comes from coding. These tendencies lead to bloated software, frequent systems redevelopment, and developer burnout.
The future of software with DDD promises to play a significant role in bringing new and far more successful models of development to life. The question is very much like the quandary that presented procedural programmers of old when object-oriented programming came on the scene and even now as functional programming is challenging the object oriented world. Will choose to innovate? Or, will we continue to defend the status quo that have arguably proven their inefficiencies? Will we learn how to grasp clean, domain-aligned, design capabilities we don’t yet understand to gain the benefits that this paradigm, DDD, offers? How quickly we answer these questions and begin to truly honor the domains we serve, will determine how quickly the benefits of the future will arrive.