![[Anemic Domain Model#^50a1a6]] Since [[Encapsulation is bundling data and behavior in a single object]], anemic domain models break [[Encapsulation]] by definition. [[Fowler, Martin|Martin Fowler]] believes the Anemic Domain Model anti-pattern is common because many developers, especially those with a data-centric background, haven't had experience working with a proper domain model. Additionally, certain technologies, like J2EE's Entity Beans, encourage this approach, which is why he prefers using POJO domain models instead. ([[References#^3a2779|Fowler, 2003]]) [[Vernon, Vaughn|Vaughn Vernon]] traces the origins of Anemic Domain Models to the influence of Visual Basic, JavaBean standards, and early ORM tools like Hibernate. These technologies popularized the use of getters and setters, which contributed to the widespread adoption of this flawed design. ([[References#^28d541|Vernon, 2013]])