Domain Logic: Where does it go?
20.9 هزار بار بازدید -
3 سال پیش
-
I'd argue most software and
I'd argue most software and domain logic is written using Transaction Scripts. Transaction Scripts are single procedures that handle a request. While this can work fairly well in a lot of cases, it starts falling apart when you have a lot of domain complexity and/or a lot of various concerns. A sign you've gone too far is difficulty testing and wanting to call a transaction script from another transaction script. When this happens, what's a solution? Encapsulating your domain logic and state changes within a Domain Model.
🔗 EventStoreDB
https://eventsto.re/codeopinion
🔔 Subscribe: https://www.seevid.ir/fa/result?ytch=UC3RKA4vunFAfrfxiJhPEplw
💥 Join this channel to get access to source code & demos!
🔥 Don't have the JOIN button? Support me on Patreon!
https://www.patreon.com/codeopinion
📝 Blog: https://codeopinion.com/
👋 Twitter: https://twitter.com/codeopinion
✨ LinkedIn: https://www.linkedin.com/in/dcomartin/
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion
https://www.seevid.ir/fa/w/PrJIMTZsbDw Intro
https://www.seevid.ir/fa/w/PrJIMTZsbDw Transaction Script
https://www.seevid.ir/fa/w/PrJIMTZsbDw Added Complexity
https://www.seevid.ir/fa/w/PrJIMTZsbDw Heuristics
https://www.seevid.ir/fa/w/PrJIMTZsbDw Domain Model
#softwaredesign #softwarearchitecture #domainmodel
3 سال پیش
در تاریخ 1400/11/06 منتشر شده
است.
20,958
بـار بازدید شده