← Graph

Domain-Driven Design

concept 33 connections

Approach originating in Eric Evans' 2003/2004 book 'Tackling Complexity in the Heart of Software'. Aligns business and code by developing a ubiquitous language per bounded context. On this panel Scott Bellware — an early DDD conference speaker from 2002 — argues that the essence of DDD (design principles, fundamentals) is valuable but that the movement has been subjugated by celebrity geeks into a ritualistic cult of elaborate tactical patterns, with specialized vocabulary that cuts practitioners off from the broader, pre-existing body of software-design knowledge (e.g. 'aggregate' displacing 'partition'). He cites Junior/mid-level developers anxious about 'doing DDD correctly' as evidence that DDD has become an end in itself rather than a means to good design. Paweł partially agrees on the vocabulary problem but argues the battle against entrenched terminology is already lost and suggests a translation dictionary between vocabularies instead.

category
methodology
talk Applying CQRS & Event Sourcing on Rails applications
about
Domain-Driven Design concept
Positions CQRS/ES work within DDD.
talk The pillars of Domain Driven Design
about
Domain-Driven Design concept
Talk is an introduction to DDD and its strategic and tactical pillars.
talk Enterprise Rails Panel
about
Domain-Driven Design concept
Discussed with bounded contexts and ubiquitous language.
talk Might & Magic of Domain-Driven Design
about
Domain-Driven Design concept
Central subject of the talk — DDD process and mindset shift.
resource Domain-Driven Design: Tackling Complexity in the Heart of Software
about
Domain-Driven Design concept
Foundational text of the methodology.
talk How wroclove.rb impacts developers and companies
about
Domain-Driven Design concept
The speaker adopted DDD after prior wroclove.rb.
resource Domain-Driven Design: Patterns, Principles and Practices
about
Domain-Driven Design concept
Practical overview of DDD strategy, modeling, and implementation.
resource Implementing Domain-Driven Design
about
Domain-Driven Design concept
Vaughn Vernon's practical DDD guide.
talk Developer, Programmer, and AI
about
Domain-Driven Design concept
Argues DDD reconciles code and business languages.
takeaway Three Steps of DDD
about
Domain-Driven Design concept
Summarizes DDD practice.
takeaway Risks of DDD: Hierarchy, Perfectionism, Constraints
about
Domain-Driven Design concept
Describes risks of adopting DDD.
question Does DDD require object-oriented programming?
about
Domain-Driven Design concept
Question probes DDD's relationship to OOP.
talk Business logic in Ruby
about
Domain-Driven Design concept
Arkency adopted DDD terminology ('aggregates') for their business-logic classes.
talk Typical DDDomains In Rails Apps
about
Domain-Driven Design concept
Entire talk pitches a layered DDD approach in Rails.
talk Strategic Domain Event Design Lightning Talk
about
Domain-Driven Design concept
Argues DDD is more than Aggregates and that models serve specific contexts
talk Events events events
about
Domain-Driven Design concept
Recommends DDD for detecting which events to store and splitting the system by domain.
talk The good, the bad and the remote — collaborative domain modeling with EventStorming
about
Domain-Driven Design concept
Gil combines EventStorming with DDD to derive aggregates, acceptance criteria, and object design.
talk Event-Driven Rails Discussion Panel
about
Domain-Driven Design concept
Extensive opening debate on whether DDD is worth using or is a celebrity-geek cult.
talk Working with RailsEventStore in Cashflow Management System
about
Domain-Driven Design concept
Uses tactical DDD patterns (aggregates, read models, processes).
talk Is the monolith a problem
about
Domain-Driven Design concept
Recommends DDD alongside DRY for better modeling.
person Andrzej Śliwa
has_skill
Domain-Driven Design concept
Speaker applies DDD with business stakeholders at his fintech.
level: expert
person Mateusz Nowak
has_skill
Domain-Driven Design concept
Eight years of applying DDD, EventStorming and Event Modeling in commercial projects.
level: expert
person Marco Heimeshoff
has_skill
Domain-Driven Design concept
Self-described as loving DDD 'to an unhealthy degree'; teaches and advocates it.
level: expert
person Adam Piotrowski
has_skill
Domain-Driven Design concept
Introduced DDD on a new project at his company.
level: intermediate
person Łukasz Szydło
has_skill
Domain-Driven Design concept
Listed as one of his specialties.
level: expert
person Mariusz Gil
has_skill
Domain-Driven Design concept
Combines DDD with EventStorming on daily client work.
level: expert
person Paweł Strzałkowski
has_skill
Domain-Driven Design concept
Pavel lists DDD as one of his daily interests.
level: intermediate
person Andrzej Krzywda
recommends
Domain-Driven Design concept
Arkency adopted DDD and refers to business-logic classes as aggregates.
person Anton Davydov
recommends
Domain-Driven Design concept
Suggests DDD as a way to split the system and choose which events to store.
person Scott Bellware
recommends
Domain-Driven Design concept
Endorses the essence/fundamentals of DDD but not its subculture and elaborate tactical patterns.
person Paweł Pacana
recommends
Domain-Driven Design concept
Arkency embraces DDD vocabulary and techniques in rails_event_store projects.
person Chikahiro Tokoro
recommends
Domain-Driven Design concept
Recommended alongside DRY-as-knowledge for better modeling.
person Eric Evans
works_on
Domain-Driven Design concept
Evans' metaphor large-scale structure (from the DDD book) is cited by Gil.
role: originator

Provenance

Created in
Applying CQRS & Event Sourcing on Rails applications — An... 2026-04-17 16:18
Last updated in
Event-Driven Rails Panel — Eventide vs rails_event_store ... 2026-04-17 22:12
Total updates
2 extractions
Read by
24 extractions