<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ddd on PolarBear</title><link>https://polar7bear.dev/tags/ddd/</link><description>Recent content in Ddd on PolarBear</description><image><title>PolarBear</title><url>https://polar7bear.dev/og-default.jpg</url><link>https://polar7bear.dev/og-default.jpg</link></image><generator>Hugo -- 0.164.0</generator><language>ko-kr</language><atom:link href="https://polar7bear.dev/tags/ddd/index.xml" rel="self" type="application/rss+xml"/><item><title>DDD 개요</title><link>https://polar7bear.dev/docs/architecture/ddd/ddd-overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/ddd-overview/</guid><description>Domain-Driven Design의 정의, 전략적 설계와 전술적 설계의 구분, 핵심 용어와 패턴 지도</description></item><item><title>Bounded Context</title><link>https://polar7bear.dev/docs/architecture/ddd/bounded-context/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/bounded-context/</guid><description>모델이 적용되는 경계를 명시적으로 정의하는 DDD 전략적 설계의 중심 패턴</description></item><item><title>Ubiquitous Language</title><link>https://polar7bear.dev/docs/architecture/ddd/ubiquitous-language/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/ubiquitous-language/</guid><description>도메인 모델을 언어의 뼈대로 삼아 대화·문서·코드가 같은 용어를 쓰게 만드는 실천</description></item><item><title>Context Map</title><link>https://polar7bear.dev/docs/architecture/ddd/context-map/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/context-map/</guid><description>Bounded Context 사이의 관계를 그리는 방법과 Shared Kernel·ACL·Open-host Service 등 9가지 관계 패턴</description></item><item><title>Aggregate</title><link>https://polar7bear.dev/docs/architecture/ddd/aggregate/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/aggregate/</guid><description>트랜잭션 일관성 경계로서의 Aggregate와 Vaughn Vernon이 정리한 4가지 설계 규칙</description></item><item><title>Entity와 Value Object</title><link>https://polar7bear.dev/docs/architecture/ddd/entity-value-object/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/entity-value-object/</guid><description>동일성 기준으로 모델 요소를 나누는 방법과 Domain Event까지, 도메인 모델의 기본 구성 요소</description></item><item><title>Repository와 Service</title><link>https://polar7bear.dev/docs/architecture/ddd/repository-and-service/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/repository-and-service/</guid><description>Aggregate 접근을 담당하는 Repository, 생성을 담당하는 Factory, 그리고 Domain Service와 Application Service의 경계</description></item><item><title>Anemic Domain Model</title><link>https://polar7bear.dev/docs/architecture/ddd/anemic-domain-model/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polar7bear.dev/docs/architecture/ddd/anemic-domain-model/</guid><description>엔티티에 데이터만 남고 규칙은 전부 Service에 있는 안티패턴. 증상과 진단, 그리고 왜 문제인가</description></item></channel></rss>