데이터 베이스를 도메인 주도 설계 방법으로 설계 하다 보면
중복되는 데이터가 생길 때 두 테이블이 하나로 합쳐 질 수 있을 때
어떻게 하나의 의문이 들어. 찾아 보았다
DDD book 의 원작자인 Eric evans 의 인터뷰 http://dddcommunity.org/news/index-html-2/
에릭 에반스의 글을 인용 하였다
Using Domain-Driven Design (DDD) to separate the concerns of a large system into bounded contexts with each context using its own data store often results in a need to share some common data, Julie Lerman recently explained in MSDN Magazine.
When Julie, a Microsoft MVP since 2003, began learning about DDD, she struggled with the duplication of data such a separation could result in, but an explanation by Eric Evans, author of the original DDD book, cleared things up:
You have to choose where to pay the price of complexity. Because DDD is about reducing complexity in the software, the outcome is that you pay a price with respect to maintaining duplicate models and possibly duplicate data