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. Added together they can put a serious overhead on the development process, substantially inhibiting the ability to develop a ubiquitous language with your domain experts.
So, Naked Objects is an open source Java framework that helps solve this problem. By taking care of the presentation, application and persistence layers, Naked Objects lets you focus on just the domain, the bit that matters. In this talk we'll see how easy Naked Objects makes it to bootstrap your DDD efforts, developing pojo-based domain models.
On the hand, adopting a framework is not a decision we should take lightly: how does it scale, what is its performance and reliability, what about support? And in the case of Naked Objects, given its generic OOUIs won't be suitable for every end-user audience, we may want to skin our domain objects with custom UIs. So we'll also discuss the various ways you can develop with Naked Objects, from being a strictly design time tool through to the full runtime stack.
Along the way, we'll also talk about some of the other integrations that Naked Objects supports, including
FitNesse , third-party frameworks such as
Wicket ,
Hibernate and
ESBs ( click on the links for related courses).
![James Grenning:TDD for [Embedded] C SOLID and Testable C,](/custom/geeks_thumb/james-grenning_small.jpg "James Grenning:TDD for [Embedded] C SOLID and Testable C")
