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:
- Eric Evans Domain Driven Design Immersion Workshop (in London on 21st - 24th September 2015)
- Conway's Law & Reverse Conway's Law - How to avoid being caught by it and how to turn it to your advantage (in London on 23rd September 2015)
- Greg Young's Advanced CQRS & DDD Workshop (in London on 28th - 30th September 2015)
- µCon 2015: The Microservices Conference (in London on 9th - 10th November 2015)
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.