Other than implementation details, are DDD aggregates similar to GoF’s facade ?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Other than implementation details, are DDD aggregates similar to GoF’s facade ?
A GoF Façade, much like a real façade, hides the underlying implementation complexity by creating another abstraction; it hides a complex and generally separate system (or subsystem) behind a simple to use interface. For example, façade for a game might have the methods start, update and pause; completely hiding the implementation of the game, but providing a high-level way to interact with it.
The DDD aggregate on the other hand is a way of specifying a "has-a" relation between objects that have a stronger correlation than normal references. They can be seen as nodes in a tree of domain objects and they are generally treated as a single unit in terms of data exchange.