THIS is been discussed in almost all multi-layered application architectures where to put most of the business logic, whether its in domain or in service. More than 80%of the time you can expect it should be a service layers due to various advocations.
This post try to throw some basic questions that everyone should consider ...
1.Is domain just a entity? Or it accompanies the domain service & value objects?
2.Can domain access other service layers? If so, hwo much can you perform unit testing?
3.How much DAO can co-hesive with domain?
4.Where to perform domain validation...is it a domain behaviour or domain service job?
5.Can you instantiate any other domains directly from domain behaviours?
6.How far we can use static in domain? Is it a good practice from unit test perspective?
7.Can a domain have additional behaviours apart from getters/setters of its state?
...of course lot more ... .
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment