1 DAY CONFERENCE

DDD eXchange NYC

Tuesday, 17th September in New York City

7 experts spoke.
Overview

Join Skills Matter and the father of DDD; Eric Evans, Greg Young (creator of CQRS), Vaughn Vernon (author of Implementing DDD) and Alberto Brandolini for an unmissable opportunity to hear about DDD and it's roadmap.

It's been 10 years since Eric Evans' book exploring Domain Driven Design was published. Eric argues the landscape has drastically changed in those 10 years; with greater emphasis on Event Sourcing and CQRS amongst the most dramatic changes. And with Vaughn Vernon's book 'Implementing DDD', there has been a renewed sense of importance attached to DDD in software.

Excited? Share it!

Programme

#dddxnyc Parkbench Panel Discussion



Steve Bohlen

Software Engineering Ronin; Sr. Technical Evangelist @Microsoft ; author Summer of NHibernate scrncasts; co-founder ALT .NET NYC; chair of @codecampnyc; mentor


PARK BENCH PANEL DISCUSSION



Steve Bohlen

Software Engineering Ronin; Sr. Technical Evangelist @Microsoft ; author Summer of NHibernate scrncasts; co-founder ALT .NET NYC; chair of @codecampnyc; mentor


Rethinking Enterprise Software



Alberto Brandolini

Alberto Brandolini can model every business domain, given enough space, a paper roll and an unlimited source of colored sticky notes (with a preference for orange ones). He calls this stuff EventStorming.


Focusing the Core Domain: Domain-Driven Design Case Study



Eric Evans

Eric Evans, author of Domain-driven Design: Tackling Complexity in the Heart of Software is a thought leader in software design, domain driven design and domain modeling and particularly focuses on strategic design.


Opening & Welcome



Eric Evans

Eric Evans, author of Domain-driven Design: Tackling Complexity in the Heart of Software is a thought leader in software design, domain driven design and domain modeling and particularly focuses on strategic design.


Simplifying integration with event-centric domain models

Very few systems complex enough to justify the use of DDD live in a vacuum, and integration with third parties or other internal systems is often overlooked. Often the cost of integrating can be greater than the cost of building a new system in the first place.



James Nugent

James is a software developer and consultant living in Bath, England. He often works on systems in industries with significant regulatory constraints, including pharmaceutical manufacturing, healthcare and energy. He is currently working on the op


How DDD became essential in the (highly competitive) energy sector

Exploring for oil is an expensive business, getting it out of the ground even more so. Discovering, describing and simulating oil reservoirs is a competitive software-intensive activity. The dominant players must provide unique advantages within the constraints of off-the-shelf software systems.

In this talk, Robert will illustrate the benefits and challenges – both technical and cultural – encountered by one company in applying DDD to “shared earth models” which were hitherto implicitly encoded in legacy systems. I’ll also discuss the all-important business imperatives that have motivated the adoption of domain modelling in the oil and gas software industry.



Robert Smallshire

Robert Smallshire is Founding Director of Sixty North, a software product and consulting business based in Norway. He has designed and implemented architectures for complex scientific and enterprise software in Python, C++, and C#, and is a regular speaker and coach.


Reactive DDD with Scala and Akka

In this talk, Vaughn will explore the use of the Actor Model with DDD. He will explain how the basic ideas of the Actor Model and DDD can greatly simplify our ability to comprehend and use concurrency and distribution.



Vaughn Vernon

Vaughn is a veteran software craftsman, with more than 35 years of experience in a broad range of business domains, Vaughn is a leading expert in DDD and champion of simplicity and Reactive systems.


DOCUMENT BASED MESSAGING AND ANALYSIS



Greg Young

Greg Young coined the term "CQRS" (Command Query Responsibility Segregation) and it was instantly picked up by the community who have elaborated upon it ever since.


SkillsCasts

Hold tight, skillscasts coming soon!

 

Other Years


Thank you to our sponsors and partners


Platinum