Home

Getting Started with Domain-Driven Design




Other Refcardz


thumb

Spring Annotations

Features include Core Spring Annotations, Spring MVC Annotations, AspectJ Annotations, JSR-250 Annotations, Testing Annotations, Hot Tips and more.


thumb

Getting Started with JavaFX

Contents Include: About JavaFX, JFXPoetry - a simple example, JavaFX Reference, Hot Tips and more...


thumb

Getting Started with Oracle Berkeley DB

Contents Include: Oracle Berkeley DB Family, Berkeley DB Java Edition Features, BDB JE Base API and Collections API, BDB JE DIrect Persistent layer, BDB JE Transaction Support and Performance Tuning, BDB JE Backup and Recovery, Hot Tips and more...


thumb

GlassFish Application Server - Updated for Version 3

Features include Installing GlassFish, GlassFish Domains Profile, Common Administration Tasks, Create a JMS Resource, Clustering and Load Balancing, Hot Tips and more.




Click Here To
Download PDF


Overview

It is often said that Domain-Driven Design is object orientation done right but the truth is that Domain-Driven Design is much more than just object orientation. Domain-Driven Design also deals with the challenges of understanding a problem space and the bigger challenge of communication that understanding.  This DZone Refcard introduces you to the key concepts, techniques, and patterns that will help you overcome these challenges.


About the Author

Aslam Khan is an architect and coach working out of South Africa.  He is part of factor10; a team software architects that help teams write software better.  With more than 18 years experience, he has learned that design is more valuable than technology, and pragmatic decisions are more valuable than rules.  He takes the position that architects should be able to build what they draw and that the only truthful implementation of an architecture is the code that gets executed.  He is particularly passionate about creating simple solutions for complex problems, and part of that passion pushes him to try to explain architecture and software development as simply as possible.  Aslam believes that good code can only be produced when there is a good balance between social and technical skills of everyone on a team.