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:
- Martine Devos' Certified Scrum Master, Estimation & Planning Class (in London on 10th - 11th October 2016)
- Martine Devos' Certified Scrum Product Owner (in London on 13th - 14th October 2016)
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 31st October - 2nd November 2016)
- Agile Testing & BDD eXchange 2016 (in London on 10th - 11th November 2016)
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.