Want to find out ways you can use types as part of a domain driven process? With real world examples in F#, come along to this no jargon, no maths, no prior F# experience necessary event.
Statically typed functional programming languages like F# encourage a very different way of thinking about types. The type system is your friend, not an annoyance, and can be used in many ways that might not be familiar to OO programmers.
Types can be used to represent the domain in a fine-grained, self documenting way. And in many cases, types can even be used to encode business rules so that you literally cannot create incorrect code. You can then use the static type checking almost as an instant unit test — making sure that your code is correct at compile time.
YOU MAY ALSO LIKE:
- Understanding Parser Combinators: A Deep Dive - Audience Level: Beginner (SkillsCast recorded in April 2017)
- Microservices Architecture with Jorge Ortiz‑Fuentes (Online Course on 15th - 17th February 2021)
- Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 18th - 19th February 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- DDDx — Domain-Driven Design eXchange 2021 (Online Conference on 8th - 9th June 2021)
- Evolutionary Architecture (SkillsCast recorded in January 2021)
- What an Architect Can Learn from Retrospective Failures (SkillsCast recorded in December 2020)
Domain Driven Design, F# and Types
Scott Wlaschin
Scott has over 20 years experience in software development, design and architecture, covering all aspects of business software.