NEW! Advanced Domain–Driven Design

2018-10-08 08:00 to2018-10-10 16:00(Europe/Paris)

--Paris, France--

Ticket TypeEnd of SubscriptionPriceQuantity
Event registration not yet started.


 

Highly professional, intense and therefore effective, opened to personal needs and questions. 

A result of this workshop, I plan to prioritize different products(=projects) in Product(s) Backlog, based on business value.  “Event Storming is truly valuable, also as an exercise. I found the patterns to separate domains and their relations very interesting. (…) I’ve discovered that DDD has many patterns and strategies that we seem to have lost. It is essential knowledge for every developer, from junior to architect. For more experienced developers (and business architects), the Strategic Domain–Driven Design workshop gives theory and experience to better deal with (business) domains, relations, Bounded Contexts, and how to map systems. Must attend!” (translated from Dutch) .Marc Van Andel, Integration Specialist / Java Architect, Kadaster (Netherlands)

REGISTREERI KOOLITUSELE ENNE 15. 09.2018

Software design can have a very slow feedback loop: by the time you find out if the architectural and design decisions you made were the right ones, it may be too late for drastic changes. As developers, we tend to phrase all problems as technical problems, which can be sufficiently challenging in their own right. We tend to lose sight of the underlying business concerns.

Domain–Driven Design is total approach to building software for complex domains. It’s a way of thinking that helps you decide how to tackle complexity, and where to focus your efforts. By putting the business at the heart of our software, and keeping our domain model closely tied to our understanding of the business, we can create value at a much deeper level.

Where

--Paris, France--

When

From2018-10-08 08:00
To2018-10-10 16:00

Trainer

DDD Europe, Mathias Verraes

Social Stream

Participate on Twitter

Find out what people see and say about this event, and join the conversation.

Use this tag: #devtraining, Domain–Driven Design