Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Why Domain-Driven Design Matters

Why Domain-Driven Design Matters

Why Domain-Driven Design Matters

In the software industry, the life expectancy of ideas, methodologies, and technologies, is extremely short. And yet, after ten years, Domain-Driven Design is still growing bigger. From it’s original roots in OOP, it has now expanded into Functional Programming, Reactive Programming and Event Sourcing, and architectural styles such as Hexagonal and CQRS. Clearly something about Domain-Driven Design makes it such an appealing choice to build systems for complex domains.

In this session, we’ll discuss what DDD is: from design patterns and modelling techniques, to the more philosophical ideas about how we deal with complexity. We explore why it has made such a profound impact, and how to decide whether it’s right for your project. We’ll have lots of room for open discussion, to make sure all your questions are answered.

--

Mathias Verraes is a recovering music composer turned programmer, consultant, blogger, speaker, and podcaster. He advises companies on how to build enterprise web applications for complex business domains . For some weird reason, he enjoys working on large legacy projects: the kind where there’s half a million lines of spaghetti code, and nobody knows how to get the codebase under control. He’s the founder of the Domain-Driven Design Belgium community. When he’s not working, he’s at home in Kortrijk, Belgium, helping his two sons build crazy Lego train tracks.

Mathias Verraes

May 20, 2014
Tweet

More Decks by Mathias Verraes

Other Decks in Technology

Transcript

  1. INFLUENCE - ORGANISATION - - SOFTWARE - HARDWARE - -

    RESPONSIVENESS TO BUGS - - CONTRACTS - THIRD PARTIES - - DEVELOPER HAPPINESS - TOOLS - - TESTS - SKILLS - COMMUNICATION -
  2. “IT IS AN AXIOM THAT INFLUENCE IS BOTH A CAUSE

    AND AN EFFECT. NOTHING IS EVER INFLUENCED IN JUST ONE DIRECTION.”
  3. “JUST CALLING IT ‘FEEDBACK’ DOESN'T MEAN THAT IS HAD ACTUALLY

    FED BACK. IT HASN'T FED BACK UNTIL THE SYSTEM CHANGES COURSE.” JOHN GALL
  4. “IGNORING FEEDBACK MERELY MEANS THAT THE SYSTEM WILL EVENTUALLY EXPERIENCE

    A MASSIVE UNPLEASANT SURPRISE (RATHER THAN A SMALL UNPLEASANT SURPRISE).” JOHN GALL
  5. “THE MORE ADAPTED AN ORGANISM IS TO PRESENT CONDITIONS, THE

    LESS ADAPTABLE IT TENDS TO BE TO UNKNOWN FUTURE CONDITIONS.”
  6. “A LARGE SYSTEM, PRODUCED BY EXPANDING THE DIMENSIONS OF A

    SMALL SYSTEM, DOES NOT BEHAVE LIKE THE SMALLER SYSTEM” JOHN GALL