Check out my new course Learn you some Lambda best practice for great good! and learn the best practices for performance, cost, security, resilience, observability and scalability.
I touched on the topic of memoization in the past in relation to doing aspect-oriented programming with PostSharp, however, with functional languages like F#, Haskell or Erlang there is no such frameworks (although PostSharp should still work with F# to some extent) to help you.
That’s not to say that you can’t do AOP in a functional language though, in fact, here’s a simple implementation of the aforementioned memoizer in F# as a higher-order function:
Here’s a FSI session that shows the memoize function in action:
Note that the memoized version of the original function f took a second to execute the first time around but then subsequent calls didn’t take anytime.
The implementation I’ve shown here is a very basic and only works for functions that takes in a single parameter, if you can think of an elegant way to make it support functions with different number of inputs please feel free to contact me as I’m very interested to hear about your thoughts.
Also, this implementation won’t work with recursive functions because when the function recurs it will be calling the non-memoized version of the function, it’ll require some special handling to make a recursive function ‘memoizable’.
In general, I don’t feel AOP is as well suited to functional programming as it is to object oriented programming, but there’s still a pocket of use cases where AOP can be beneficial. Memoization is one of them, so is tracing and input validation, all of which is possible through the use of higher-order functions. A word of warning though, If you’re familiar with frameworks such as PostSharp, the AOP experience you’re going to get through higher-order functions is not going to be as unobtrusive as you’re used to.
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, 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. Enrol now and enjoy a special preorder price of £9.99 (~$13).
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 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