You can become a serverless blackbelt. Enrol in my course Learn you some Lambda best practice for great good! and learn best practices for performance, cost, security, resilience, observability and scalability. By the end of this course, you should be able to make informed decisions on which AWS service to use with Lambda and how to build highly scalable, resilient and cost efficient serverless applications.
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 podcast Real-World Serverless where I talk with engineers who are building amazing things with serverless technologies and discuss the real-world use cases and challenges they face. If you’re interested in what people are actually doing with serverless and what it’s really like to be working with serverless day-to-day, then this is the podcast for you.
Check out my new course, Learn you some Lambda best practice for great good! In this course, you will learn best practices for working with AWS Lambda in terms of performance, cost, security, scalability, resilience and observability. We will also cover latest features from re:Invent 2019 such as Provisioned Concurrency and Lambda Destinations. Enrol now and start learning!
Check out my video 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. There is something for everyone from beginners to more advanced users looking for design patterns and best practices. Enrol now and start learning!
Are you working with Serverless and looking for expert training to level-up your skills? Or are you looking for a solid foundation to start from? Look no further, register for my Production-Ready Serverless workshop to learn how to build production-grade Serverless applications!
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 wrong about serverless and vendor lock-in
- You are thinking about serverless costs all wrong
- Just how expensive is the full AWS SDK?
- Many faced threats to Serverless security
- We can do better than percentile latencies
- 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
- Top 10 Serverless framework best practices