New answers tagged

1

You are right when saying that the model should not contain anything off-topic and should contain its data "tightly". However, this has nothing to do with persistence or any implementation-specific models. The domain model is what you would use to explain your system to someone who has no idea about your programming language or frameworks. In best case, you ...


5

Technically, you are free to design the layers in your architecture however you want, but keep in mind transactions express some kind of business logic. If you put business logic into the UI, you make it much harder to write automatic tests for it, since you restrict yourself to tests you can create with an UI testing tool. This typically means ...



Top 50 recent answers are included