Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It is inherently flawed though, isn't it? It assumes you're in just one big schema, surely? Part of DDD is breaking that assumption and fragmenting your systems into the disparate domains withing your org, fully encapsulating your domains' functionality and data.

As someone else said, it's probably better to start with what events drive your org. What are the communication channels and triggers for those events.



This is exactly the point that I routinely see fail in organizations doing "DDD", it's closer to the absolute opposite of DDD in fact.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: