Nick is a technical leader who embraces every aspect of discovering, designing and continuously delivering high-scale software systems to growing and leading highly-autonomous software engineering organisations. He has been a practitioner of DDD for almost a decade, and is the co-author of two books: Patterns, Principles and Practices of DDD (Wrox), and Designing Autonomous Teams and Services (O’Reilly).
(Talk, Main Conference)
There are many attributes that define bounded contexts. Some bounded contexts are characterised by their business value - the infamous core domains. Other bounded contexts are characterised by their dependency relationships - like octopus contexts, or their relationship to legacy parts of the system - like bubble contexts.
When you study many domains and software systems, you discover more and more attributes that define bounded contexts. There are at-least 50, possibly even hundreds. You also start to see that attributes cluster giving rise to design patterns - like engagement contexts, and evolutionary transformations - like slice-and-scale.
Being able to dissect bounded contexts and deeply analyse their many characteristics - related to business value, domain complexity, technical implementation and social influence - helps you to see more and better modelling options when designing and evolving bounded contexts.
Don’t limit yourself to a few naive attributes like size, similarity, or naming patterns. Learn how to dissect every aspect of bounded contexts, and learn the patterns that demonstrate common and exotic clusterings of behaviours.
(Hands-on Lab, Main Conference)
Kacper Gunia, Nick Tune
Join us for an session of hands-on DDD modelling in the domain of loyalty.
Working in small teams of up to four, from an initial set of requirements and with domain experts available at all times you will design a system: the bounded contexts, the domain flows, technology choices, and other architectural details. However...
Don’t expect an easy ride. With whimsical stakeholders and a competitive market, requirements and product vision may (they definitely will) change at any time. Are you up for the challenge of designing and evolving your system?
There is no strict format to the session. Before the workshop begins we will look at a few of the techniques you can use to model domains including context maps, Domain Storytelling, The Bounded Context Canvas, and C4 Software Architecture. But in your teams, you will have total freedom to design the system however you want using whichever tools and techniques you prefer.
During the workshop there will be short breaks, both to get some fresh air and to take a step back on the challenge, comparing the designs and processes of each team. Maybe we will invent some new DDD modelling techniques.
More About the Domain
You are working for a fast-casual restaurant chain called “Foodanic” serving organic meals and beverages. Your core customers are office workers grabbing a cup of coffee when getting to the office and having a quick lunch to go or eat in during the noon break.
Unfortunately the company's value proposition of serving high quality and healthy food isn’t enough. More and more competitors are offering organic food in the same price range and customers attracted by other options choose alternatives.
In order to increase the consumer retention your company decided to introduce a loyalty program. Goal is to encourage customers to come back more often and reward them for it with number of redemption options.
(Two Day Pre-conference Workshop)
This is a pre-conference workshop. Click for details.