Sharing a model between client and server

Question

Thanks to our model and domain process, we are considering a model of exchange between a client and a server. Our customer is really a fat customer. Is there any information about this architecture, the pros and cons?

Answer 1

Theoretically, if your domain level is completely decoupled (due to perseverance, presentation, infrastructure, etc.), it can be easily used as a library in different places.

However, as Adrian points out, this raises practical issues:

• : , , . - , .

• : , / . , , .

• : , , , , .

, -, , , . / , ... , , , , - . , , , .

, Domain Driven Design - , .

Answer 2

DDD , . , , GUI .

- .

. , , ( ) .

, , . (, , ), , , .