Is Maybe an Option (for modelling your domain)? - Roman Sachse - KanDDDinsky 2019 @KanDDDinsky
Is Maybe an Option (for modelling your domain)? - Roman Sachse - KanDDDinsky 2019  @KanDDDinsky
Uploaded December 2019 | Updated November 2026, 1 day ago
Null is used to model a variety of states within an application. Be it to model the absence of a field in a database table, the return value when parsing something unparsable, an unsuccessful API call or to initialize some fields empty because the “ORM expects it that way”. The problem with null is that it is never completely clear to the developer whether something can or should be null at some point of the application and what null means in a specific case. Most statically typed functional programming languages avoid the problem completely by not allowing null at all. They introduce a new data type called Option or Maybe which allows us to lean on the compiler to check whether we forgot to handle the unexpected absence of a value. This leads to a greater trust in our applications and reduces runtime errors tremendously. Options can also be used to help modelling our domain but often they lack clear semantics of why a value is absent in a specific situation. Luckily options are just a small subset of the beautiful concept of sum types. Those sum types allow us to model different states of our application with ease and great expressiveness. Furthermore they allow us to get rid of many errors that are usually modelled with exceptions by taking care of them in our domain model. This talk will give you the ability to get rid of nulls with options and abstract over this concept with the help of sum types to make your code more expressive and your domain model easier to comprehend for your team and for the business.
Is Maybe an Option (for modelling your domain)? - Roman Sachse - KanDDDinsky 2019Domain Modeling Made Functional - Scott Wlaschin - KanDDDinsky 2019KanDDDinsky Keynote 2017 - Alberto BrandoliniResilience Design Patterns - Indu Alagarsamy - KanDDDinsky 2019Lessons learned from introducing Team Topologies - Michael PlödAI and Tackling Complexity - Eric Evans - KanDDDinsky 2025Design in the small  - Yves Reynhout - KanDDDinsky 2017Event Sourcing: dealing with an eventful past - Hannes Lowette - KanDDDinsky 2025Bourdieus social theory applied to tech - Romeu MouraHow a deeper model enables breakthroughs in product dev. - Kenny Baas-Schwegler & Bruno BoucardFunctional Programming and Domain Driven Design - a match in Heaven! - Marco Emrich - KanDDDinskyDDD, Event Sourcing and Actors - Alexey Zimarev - KanDDDinsky 2019
KanDDDinsky |

Is Maybe an Option (for modelling your domain)? - Roman Sachse - KanDDDinsky 2019

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER