KanDDDinsky 2019
| title | author | length |
|---|---|---|
| KanDDDinsky 2019 | 02m | |
Short, informal reflection on practice over rules that argues for learning by doing and deliberately trying things to see how they fail then improve… | ||
| Resilience Design Patterns | Indu Alagarsamy | 37m |
Translates climbing anchors to software: use SERENE (Solid, Redundant, Equalized, No extension) so critical services are duplicated, load balanced and avoid… | ||
| Accelerate | Marcello Pauli | 38m |
Greenfield slice for legal-protection integrates with an existing data-acquisition system and replaces a failing vendor magic library by designing a custom… | ||
| DDD, Event Sourcing and Actors | Alexey Zimarev | 49m |
Describes implementing event sourcing with C#, EventStore and Proto.Actor, replacing per-command stream reads by actors that hold aggregate state in memory and… | ||
| Architecture: The Stuff That's Hard to Change | Dylan Beattie | 48m |
Argues that software architecture is literally architecture is the stuff that's hard to change: make decisions, communicate them, and enforce them. Recommends… | ||
| Make your tests tell the story of your domain | Mads Opheim, Anne Landro | 49m |
Legacy Norwegian court system runs 16 years of production with few bugs; the team automates the tedious quarter‑long manual regression cycles by writing value… | ||
| Domain Modeling Made Functional | Scott Wlaschin | 51m |
Shows how using F# and composable types (options, wrapper types, discriminated unions) turns vague fields into enforced invariants: email becomes EmailAddress… | ||
| Bounded rationality, complex Systems and Agile principles | Marco Consolaro | 47m |
Argues that bounded rationality limits decisions and Agile works by expanding those boundaries through faster feedback and shared models. Cites a supermarket… | ||
| How we changed our world | Carola Lilienthal | 39m |
Developer community claims concrete wins: unit testing (JUnit in 1997) cuts late bugs, the Agile manifesto (2001) shifts feedback into short cycles, DevOps… | ||
| Is Maybe an Option (for modelling your domain)? | Roman Sachse | 43m |
Shows that F# option/maybe makes absence explicit but not why a value is missing, and that replacing scattershot nulls with algebraic sum types (like a custom… | ||
| Domain Prototyping or Design Is How It Works | Tobias Goeschel | 50m |
Starts by arguing for building a tiny, working domain core first and iterating outward: event storming to choose a small bounded context, implement a… | ||
| Context Maps - a deep dive | Michael Plöd | 49m |
Context maps deliver a practical map of how bounded contexts and teams actually interact, exposing which models propagate (loan application form → scoring)… | ||
| Cut & Shave | Herman Peeren | 47m |
A domain model for a hot‑air balloon operator gets pared back to reduce accidental complexity: invoices, invoice lines, time and space and team‑spirit are… | ||
| Meet the Social Side of Your Architecture | Adam Tornhill | 46m |
Argues that version-control data reveals hidden organizational faults using fractal figures and a normalized 0–1 team-coupling metric to detect modules with… | ||
| Desigining better processes and customer journeys with DDD and Event Storming | Francois Royer | 47m |
Shows two concrete wins: use Event Storming to extract event models from messy BPMN and customer-journey artifacts, reverse-engineer deployed workflows into… | ||
| Hatching software development ecosystems (the gordian knot) | Alberto Brandolini | 53m |
DevOps adopters deploy up to 46x more frequently and achieve commit‑to‑deploy lead times up to 400x faster, while success correlates with loosely coupled… | ||
| A practical introduction to DDD, CQRS & Event Sourcing | Dennis Doomen | 44m |
Shows a concrete mortgage application model: a MortgageApplication aggregate that enforces the invariant “all proofs must be signed” with optimistic… | ||
| Extreme Contracts: free to work the way we love toward the right design | Jacopo Romei | 46m |
Proposal: run 5-day paid spikes at a fixed, non-negotiable price; customer pre-allocates budget, inspects deliverable at end of each iteration and either pays… | ||
| Finding your service boundaries - a practical guide | Adam Ralph | 49m |
Argues that service boundaries come from use cases not entities and shows a concrete pattern: in an Amazon-style checkout create the order ID at workflow start… | ||
| Functional Programming and Domain Driven Design - a match in Heaven! | Marco Emrich | 51m |
Shows how Domain-Driven Design concepts are encoded as pure functions and types, with concrete examples in ReasonML and TypeScript. Implements Hexagonal… | ||
| Visualizing Cloud Systems | Lynn Langit | 45m |
Argues that concrete visual system views cut delivery time and debugging effort, showing several concrete wins: an IoT project goes from four years of failed… | ||
| Pitching DDD to the management | Michael Plöd | 48m |
Practical script and evidence for pitching Domain‑Driven Design to senior management: cite the Accelerate study linking loosely coupled architecture and org… | ||
| Keynote: What really matters | Jimmy Nilsson | 01h 00m |
Outlines five concrete priorities for successful projects: start with purpose, align to business context, focus on the language (ubiquitous language and even… | ||
| nothing matches | ||