Is an ANEMIC Domain Model really that BAD?
Is an anemic domain model a bad thing? Most would probably call it an anti-pattern, and it should be avoided. But is that really true? Well, it depends on what your intent is. Are you trying to create a domain model? Or are you really just trying to create a data model? 🔗 EventStoreDB https://eventsto.re/codeopinion 🔔 Subscribe:    / @codeopinion  💥 Join this channel to get access to source code & demos!    / @codeopinion  🔥 Don't have the JOIN button? Support me on Patreon!   / codeopinion  📝 Blog: https://codeopinion.com 👋 Twitter:   / codeopinion  ✨ LinkedIn:   / dcomartin  📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo... 0:00 Intro 0:31 Anemic Domain Model 4:49 Transaction Script 7:08 Domain Model #softwarearchitecture #softwaredesign #domaindrivendesign

SOLID Principles? Nope, just Coupling and Cohesion

Rich domain model. What does that even mean? Why is it useful?

What makes an Aggregate (DDD)? Hint: it's NOT hierarchy & relationships

This Is How the Anemic Domain Model Turns Bad

Stop Building 'God Objects': Use Shared Identity Instead

The Modular Monolith: Scale Without Microservices

Why Your Event-Driven Design Is Failing

Kill Anemic Domain Models with Encapsulation: The Hard Part

Is Domain-Driven Design Overrated? • Stefan Tilkov • GOTO 2021

Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker

DDD & LLMs - Eric Evans - DDD Europe

Domain-Driven Design: The Last Explanation You'll Ever Need

Android 17 sucks. So I put Linux on a phone.

How Instagram Scaled Postgres to 2 Billion Users

Google & AWS Veteran: What Top Tier Software Architects Do Differently

How To Use Domain-Driven Design In Clean Architecture

Billionaire's WARNING: I'm SELLING. The Crash Is Already Here!

Tired of Layers? Vertical Slice Architecture to the rescue!

Is an Anemic Domain Model an Anti-Pattern?

