Aleix MorgadasWhich are the concepts you misunderstood from #DDD that took you the most to realize it was wrong?
I start.
I recall reading Implementing Domain Driven Design for first time around 2014. My English wasn't the best and I started as a developer recently, so, my exposure to different concepts and names was limited.
I recall reading a lot about Model-View-Controller architecture back then because I started as an Android Developer and everything about architecture was that.
Later on, I applied the same #MVC to backend, starting with Laravel which it had also this architecture well integrated into the framework.
So, as I was reading about #DDD, it focused on the importance on working on the #DomainModel. So, for me, the Domain Model was the Entity you have in the code but without getters and setters!
I was proudly building reach Domain Models (very big Entities) with a lot of unit tests because they needed to be useful even though they were imperfect.
So, in my mind, I was creating reach domain models that were exposed via a REST controllers.
I ended up creating very big "Entities" because they needed to represent the world. So, they were doing more than they should do just because I misunderstood:
Domain Model == Model Layer in the Architecture without getters and setters.
It took me 2 to 3 years to realize that 
Daniel Solé
