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.
If you enjoy reading these exercises then please buy Crista’s book to support her work.
Style 12 – Closed Maps
- Larger problem is decomposed into things that make sense for the problem domain
- Each thing is a map from keys to values, some values are procedures/functions
- The procedures/functions close on the map itself by referring to its slots
First, let’s define what a Map constitutes to in our solution and the three things we need:
Then let’s add to the dataStorageObj map (this is analogous to the DataStorageManager in the Things and Letterbox styles). Here we’ll map the “init” key to a function that extracts the words from the specified path and stores the result as a string in the “data” key.
Next, let’s do the same for the stopWordsObj map:
and the wordFreqsObj map:
Finally, we need to initialize both dataStorageObj and stopWordsObj maps (notice that we need to first cast each value to a function signature and then invoke it with an argument, pretty ugly…):
and then count anything that’s not a stop word, and print the top 25:
These last couple of lines should be encapsulated into another map that’s analogous to the WordFrequencyController in the Things style. The reason I didn’t do this was because I wanted to stay faithful to Crista’s example where she chose not to for some reason.
Whilst this was another interest twist to the OOP paradigm that we (as .Net developers) are used to, like the Letterbox style it’s also very much at odds with how one would idiomatically approach thing in F#. As a style, we also didn’t get a chance to explore other possibilities that often come with this style – namely prototypal inheritance and monkey patching.
You can find the source code for this exercise here.
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. We will also cover latest features from re:Invent 2019 such as Provisioned Concurrency – what it is and when you should use them. 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 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