Domain-driven design continues to gain momentum as a way of building enterprise applications, but that doesn't mean it's easy to do. The strict layered architecture demanded by DDD means that domain logic must stay in the domain, but those other layers still need developing one way or another.
YOU MAY ALSO LIKE:
- Simulating APIs for Effective Testing: (Micro) Service Virtualization in the 21st Century (in London on 1st March 2017)
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 9th - 10th March 2017)
- Test all the things with Intern 4 with Dylan Schiemann! (in London on 15th March 2017)
- DDD eXchange 2017 (in London on 27th - 28th April 2017)
How to have your domain-driven design cake and eat it, too
Dan is a freelance consultant, developer, writer and trainer, specializing in domain-driven design, agile development, enterprise architecture and also REST, on the Java and .NET platforms. Dan is known as an advocate of the naked objects pattern, and is the lead committer to Apache Isis, a Java framework that implements the naked objects pattern. He also works (for a client) on an app that runs on top of Isis, called Estatio. You can find Estatio up on github; it also is open source.