Finding The Sweet Spot

B8d45998626d3dd3c582c4aeee792e2d?s=47 Andrew Best
August 12, 2017
Programming
0
170

Finding The Sweet Spot

DDD, CQRS, and ORMs - Finding the sweet spot between these development techniques

B8d45998626d3dd3c582c4aeee792e2d?s=128

Andrew Best

August 12, 2017
Tweet

Want more?

B8d45998626d3dd3c582c4aeee792e2d?s=48 andrewabest
0
32
B8d45998626d3dd3c582c4aeee792e2d?s=48 andrewabest
1
150
B8d45998626d3dd3c582c4aeee792e2d?s=48 andrewabest
2
79
7cbd3f5f922d798cc312eaf596de7ae6?s=48 iamctodd
2
530
3ab1249be442027903e1180025340b3f?s=48 reverentgeek
14
880
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
6
480
766b9746b59e6f09e280cd33cf4ed419?s=48 skipperchong
0
300
61857dafbd287b3027c4dcea9008ad3c?s=48 carmenhchung
8
620
06f8b41980eb4c577fa40c41d5030c19?s=48 keathley
9
330
C0390e8b11079f8761c0cd3274ed61cb?s=48 productmarketing
3
360
C35e01544a0dd94a2cf1619ee8a42ebb?s=48 clairelew
5
910
6bb82b13cda86d3b821fa44100335ddf?s=48 thoeni
1
230

Transcript

  1. 1.

    Community Partners

  2. 2.

    12 August 2017 | Andrew Best

  3. 3.

    Domain Driven Design At it’s heart, DDD is about TAMING

    COMPLEXITY It allows us to reason about the software we are building, explicitly modelling our problem domain in unambiguous terms and supplying well-defined semantics for its concepts. August 17 2
  4. 4.

    Meet the > Our domain model facilitates the real-world process

    requirements from our problem domain – This is what it should be doing > Our applications’ demands on their persisted state extend beyond our domain model – Task-based UIs, Reporting, Exporting, etc. > Often the domain model becomes the single façade over our persistence layer – it is set to work servicing these additional demands as well > It then becomes MORE COMPLEX > It then becomes HARDER TO REASON ABOUT > And then you add an ORM August 17
  5. 5.

    “ Object/relational mapping is the Vietnam of Computer Science Ted

    Neward http://blogs.tedneward.com/post/the-vietnam-of-computer-science/
  6. 6.

    The Codes, Part One: Death to the Repository!

  7. 7.

    CQRS >Event Sourcing >Eventual Consistency >Asynchronous Messaging >Separate Persistence Mechanisms

    August 17
  8. 8.

    CQRS >Using separate conceptual models to read and write information.

    >fin August 17
  9. 9.

    The Codes, Part Two: The Sweet Spot

  10. 10.

    CQRS >Read and write concerns truly separated >Can co-evolve without

    side effects >Minimal additional complexity >Use the best tool for the job August 17
  11. 11.

    DDD >No longer have composite UI/other concerns polluting our domain

    >Disconnects our domain model >Can better enforce consistency boundaries >Further reading: http://dddcommunity.org/library/verno n_2011/ August 17
  12. 12.

    Abstraction >Removed the potential foot- gun of complex EF queries

    >Humans struggle with DSLs >Can write tailored, specific queries that suit individual demands >But what about that type safety we just gave up? >Well… August 17
  13. 13.

    The Codes, Part Three:

  14. 14.

    Thank You! @_AndrewB https://github.com/andrewabest

  15. 15.
    None