If you enjoy reading these exercises then please buy Crista’s book to support her work.
Style 14 – Hollywood
- Larger problem is decomposed into entities using some form of abstraction
- The entities are never called on directly for actions
- The entities provide interfaces for other entities to be able to register callbacks
- At certain points of the computation, the entities call on the other entities that have registered for callbacks
I’m not overly fond of Crista’s Python interpretation of this style, so I decided to do something slightly different using F#’s built-in support for Observables. You could also use Rx via FSharp.Control.Reactive, though it seemed to be overkill for this particular problem.
Sticking with the same entities Crista defined in her example:
in our F# version, each will subscribe to an upstream IObservable, does whatever it needs to do and provide the output also as an IObservable for downstream entities.
And upstream of all the entities is an attempt to run a term frequency analysis against a data file and a corresponding stop words file:
Our version of DataStorage would depend on an IObservable<RunArgs>. It’ll in turn expose an IObservable<RunArgs * string> as member so downstream entities can subscribe to and be notified when DataStorage is able to load the words from the specified data file.
Next, we’ll implement a StopWordsFilter type that will:
- subscribe to an IObservable<RunArgs * string>;
- on a new value, load the stop words and use them to filter the words from the data file;
- make the filtered words available to downstream entities via an IObservable<string>
Finally we have the WordFrequencyCounter, which takes an IObservable<string> and print the top 25 most frequent words:
To string everything together, we’ll create an instance of IObservable<RunArgs> via an F# Event (Event.Publish gives us an instance of IEvent<‘T> which inherits from IObservable<T>).
This IOservable will act as the upstream to DataStorage and to kick things off we just have to trigger a new event with an instance of RunArgs:
You can find the source code for this exercise here.
Enjoy what you’re reading? Subscribe to my newsletter and get more content on AWS and serverless technologies delivered straight to your inbox.
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
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, 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