An overview of transaction script, anemic domain model, and domain model. See also: https://gist.github.com/hombredequeso/c2e5f77d9aac716376292defb7d9e1b8

1. A Tale of Three Architectures
It was the best of times, it was the worst of times, it was
the in between times…
Charles and Mark, 1859/2017

2. …you’re on ten here, all the way up, all
the way up – you’re on ten on your
guitar, where can you go from there?
Nowhere, Exactly. What we do is, if we
need that extra push over the cliff, you
know what we do?
Eleven.
Nigel Tuffnell, 1984.

3. Sometimes we think we are going to
eleven, but actually we are just getting
pushed over the cliff.
Mark Cheeseman, 2017.

4. •Transaction Script
•Anaemic Domain Model
•Domain Model

5. Turning it up to 11...
https://gist.github.com/hombredequeso/c2e5f77d9aac716376292defb7d9e1b8?ts=2

6. Escaping the Problems of Transaction Script
1. Focus on business operations, not data mutation.

7. Escaping the Problems of Transaction Script
2. Only allow objects in a valid state to come into existence.

8. Escaping the Problems of Transaction Script
3. Only mutate data in the context of an explicit business
operation.

9. Escaping the Problems of Transaction Script
4. Severe the connection between business/domain model and
database

10. Martin Fowler, Patterns of Enterprise Application Architecture

11. By Ktrinko - Own work, CC0, https://commons.wikimedia.org/w/index.php?curid=17169364

12. Public Domain, https://commons.wikimedia.org/w/index.php?curid=2139090

13. Presentation
Application
Data Access

14. Presentation Application
Data
Access

15. Web Page
Application
Data
Access
Web API
FTP Directory

16. Web
Controller
Core
Business
Domain
Data
Access
API Controller
FTP Directory
File Source/Data
Stream
Processor
Browser
App1 App2 App3

17. Vaughn Vernon, Implementing Domain Driven Design