← Graph

Is building DDD from scratch too slow for the business?

question 2 connections

Audience asks whether setting up this architecture is too slow to justify to the business compared to a typical Rails jumpstart. Krzywda: Rails lets you be very fast for the first few weeks, then dramatically slower — a trap for both business and developers. His mission is to simplify DDD tooling so you can be just as fast end-to-end. Most of the time is getting used to thinking in commands/events, not typing. In legacy projects, start by introducing one event at a time (e.g. price-changed → send email to clients) — that's already easier than the 'Rails way'.

answer_summary
Yes, upfront overhead exists, but the Rails 'fast first weeks, slow later' curve is the real trap. Simplifying tooling is the mission; gradual introduction via events in legacy codebases already beats the Rails way.
question Is building DDD from scratch too slow for the business?
about
Contrasts DDD setup speed with Rails' initial velocity.
question Is building DDD from scratch too slow for the business?
asked_at
Asked during Q&A.

Provenance

Read by
4 extractions