KanDDDinsky 2022
| title | author | length |
|---|---|---|
| KanDDDinsky 2022 | 03m | |
KanDDDinsky 2022 positions itself as Germany's first Domain-Driven Conference now in its 5th edition and claims a size that makes networking practical rather… | ||
| Culture - The Ultimate Context | Avraham Poupko | 51m |
Argues that culture is the ultimate context for language and therefore for software modeling, making two concrete claims: collaboration requires shared… | ||
| Road-movie architectures | Uwe Friedrichsen | 46m |
Claim: chasing a single homogenized “target architecture” repeatedly multiplies complexity and fails. Evidence: organizations hit thousands of live systems… | ||
| Start with DDD when you have a monolith | Javiera Lazo | 37m |
Uses event storming to find domains and bounded contexts, then targets the worst pain — booking — and spends about eight months to the first delivery. Applies… | ||
| Domain modelling made simple: Functions and Values | Isaac Abraham | 46m |
F# code models a train-booking domain in about 40 lines, using single-case unions to prevent mixing IDs and names, discriminated unions to encode mutually… | ||
| Systems Thinking by combining Team Topologies with Context Maps | Michael Plöd | 45m |
Combines Team Topologies’ four team types and interaction modes with Context Maps’ nine relationship patterns to make specific tradeoffs visible: use open host… | ||
| Architecture for Flow with Wardley Mapping, DDD, and Team Topologies | Susanne Kaiser | 47m |
Combines Wardley mapping + Domain‑Driven Design + Team Topologies to turn a monolithic online‑school prototype into modular bounded contexts, form… | ||
| From bi-annual to fortnightly releases in 4 months for 15 teams and one monolith | Thierry de Pauw | 47m |
15 teams sharing a 20‑year Java monolith move from bi‑annual to fortnightly releases in four months by using Improvement Kata, Value Stream Mapping and Theory… | ||
| Team evolution with DDD and Dynamic Reteaming | Ornela Vasiliauskaité | 49m |
At Vinted a three‑team monolith effort shifts from a big modularization project to incremental bounded context extraction using DDD the team merges the three… | ||
| Thriving in complexity | Trond Hjorteland | 51m |
Argues that shifting from a machine model to open systems and social science methods produces resilient organizations, not just rhetoric. Uses 1960s… | ||
| 404 Model not found: Livecoding | Thomas Coopman | 52m |
A TypeScript livecoding refactor turns a prototype price service for a Belgian recycling center into small domain objects: the code extracts PriceCalculation… | ||
| Connascence: beyond Coupling and Cohesion | Marco Consolaro | 48m |
Connascence gets defined with a three-axis taxonomy — degree, locality, strength — and concrete kinds: name and type, position, value, meaning, algorithm… | ||
| Improving Your Model by Understanding the Persona Behind the User | Zsófia Herendi | 37m |
Claim: knowing distinct personas changes how subdomains and UX are modelled and can expose why expert users avoid your product. Concrete evidence: an expert… | ||
| How to relate your OKRs to your technical real-estate | Marijn Huizendveld | 48m |
Combines OKRs with a Wardley Map to turn objectives into testable hypotheses linked to technical constraints, drawing chains of needs and plotting components… | ||
| Design and Reality | Mathias Verraes | 54m |
An oil‑rig monitoring system logs alarms as if incidents end when the alarm is silenced, so engineers invent an alert condition concept that decouples domain… | ||
| EventStorming from the trenches | Jacopo Romei | 50m |
A family-owned tank manufacturer gets a four-workshop program that uses EventStorming plus the Dot Game, Quest, extreme contracts and Popcorn Flow to map… | ||
| Architect(ure) as Enabler of Organization’s Flow of Change | Eduardo Da Silva | 43m |
Argues organizations must evolve their architecture topology across nested scopes (teams, products, product groups, portfolios) rather than treat architecture… | ||
| Actors can rule your DDD world | Hannes Lowette | 50m |
Builds BeerSender.net using .NET 6 and Akka.NET to implement event-sourced aggregates with CQRS: actors hold aggregates, persistence IDs must be unique… | ||
| Reliable messaging in the world of actors | Vagif Abilov | 48m |
Shows a concrete engineering journey building a production file-distribution engine (F#, Akka.NET, RabbitMQ and Azure Service Bus) that starts with… | ||
| Data Mesh | Jochen Christ | 44m |
Claims that domain teams own analytical data and ship data products using a self-serve platform, with governance and policies automated. Example: an e‑commerce… | ||
| Domain Driven Design in Cloud Native Environments | Tobias Goeschel | 50m |
Argues that many tactical DDD patterns break on cloud native platforms and shows concrete adaptations: bounded contexts map to accounts/VPCs or clusters… | ||
| Aligning Bounded Contexts with Subdomains in Legacy Code | Mufrid Krilic | 50m |
A legacy healthcare prescribing system reveals a new subdomain for handling non‑approved medication approvals using Domain Storytelling and the 4+1… | ||
| Balancing Coupling in Software Design | Vladik Khononov | 51m |
Argues for using coupling as a design tool and introduces an integration strength model with four levels: implementation, functional, model, contract; combines… | ||
| Domain Driven Rearchitecting with the "Domain-from-Legacy" Canvas | Matthias Eschhold | 44m |
Shows how Domain-Driven Design (DDD) can modernize an application architecture by transforming a monolithic, layer-organized system into a domain-structured… | ||
| You don't need an Event Sourcing framework. Or do you? | Alexey Zimarev | 52m |
Argues that teams usually end up building reusable plumbing for production event sourcing and so a .NET Event Store DB / Postgres / SQL Server library is… | ||
| Do Distributed Systems they said. It'll be fun they said. | Sara Pellegrini, Milan Savic | 45m |
Four years of building an event store and messaging platform reveal concrete fixes: used Raft for consensus and replication across nodes, idempotent commands… | ||
| 8 years of EventSourcing/CQRS @ bettermarks: The good, the bad and the ugly | York, Ya'ar, Saurabh | 47m |
Bettermarks recounts eight years running EventSourcing/CQRS for an adaptive maths platform with ~500,000 users per year and ~700,000 weekly “aha” events… | ||
| Events, Workflows, Sagas? Keep Your Event-driven Architecture Sane. | Lutz Huehnken | 39m |
A common order example shows an order requiring inventory and payment checks; implementing that as a centralized workflow or Saga (using Temporal, Camunda… | ||
| Juggling 300 integrations while scaling to 10mil. Signals per day | Christian Folie, Daniel Weller | 51m |
A team builds an F# service on GCP using serverless components (Cloud Functions / App Engine) to ingest and normalize over 10,000,000 GPS signals per day from… | ||
| Slow Event Sourcing reprojections? Just make them faster! | Dennis Doomen | 42m |
Practical tactics for speeding reprojections: make projectors asynchronous or project stream-by-stream to batch writes; use ORMs with batched flushes… | ||
| Learning to Love DDD - a Tale of Two Products | Chris Simon | 39m |
Compares two products: Flexischools (launched 2008, ~2 million users) used a hyper‑generic order/item hierarchy that treats a T‑shirt size like a sandwich… | ||
| KanDDDinsky Open Space | 02m | |
Open space unconference runs with people writing session ideas on Post-It session pitches then lining up to announce them and stick them on a blank agenda wall… | ||
| nothing matches | ||