One of the problems with using F#’s Discriminated Unions is that they are not extensible, in that all your union cases must be specified inside one Discriminated Union (abbreviated to DU from this point) type and you can’t inherit from an existing DU type to add additional union cases.
In most cases, having to specify all your union cases inside one DU type makes perfect sense and I’m sure there is a very good reason for the language designers to not allow inheritance with DU types.
However, sometimes I do find myself wishing for some extensibility so that I can keep using DU types instead of having to revert back to a complex class hierarchy.
Suppose you have a messaging application, you can define the different types of messages your system understands as a DU:
However, as the application grows you might want to add more specialized types of messages, and you don’t want to add them to MessageTypes to stop it from becoming bloated and to keep the specialized message types closer to code that actually understand them.
So what do you do in that case? Go back to using a class hierarchy? Sure, that’s one approach.
Another approach to this problem is to use marker interfaces, so the above code becomes:
The fact that DU types can implement interfaces is often overlooked but you can make good use of it here to enable some extensibility to your DU types.
Notice how the function f is changed from pattern matching the union cases to pattern matching against the type of the message (similar to how you can use pattern matching in a try-with block) before passing the massage to the appropriate handler function that understands that specific type.
Well, thank you for reading and hope this post proves to be helpful to you
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong