Monday, February 2, 2009

DDDD, un paso adelante

Distributed Domain Driven Design me está pareciendo la arquitectura más completa y realista. Tiene una respuesta (en forma de patrón) para cada aspecto, y no permite que la arquitectura implique una seria afectación de la eficiencia, como es el caso del DDD que he venido aplicando hasta ahora.

El fórum de discusión es muy activo, y Udi Dahan y Greg Young aclaran todas las dudas con muchísima seguridad y lógica.

Estoy entusiasmado con esta nueva opción. Este es mi resumen:

From Udi:

"The problem is thinking about the form as editing the underlying entity.
Think of the form as the way the user tells the system which task they wish to perform.
A command from the user.
Push that command down through your architecture."

"No manipulating domain objects directly on the client in a distributed system.
Changing data involves sending a command to a “service” (not SOA)."

"Even if you went to the server, right then and there, and got the most up to
date data, a second after the user looks at it - it's already stale.
Somebody else may have changed it - unless you're doing pessimistic locking."

"Just use Guids to identify your entities and you’re all set in terms of correlation – no need to wait for the server to give you an Id back."

No comments: