If you enjoy reading these exercises then please buy Crista’s book to support her work.
Style 15 – Bulletin Board
- Larger problem is decomposed into entities using some form of abstraction
- The entities are never called on directly for actions
- Existence of an infrastructure for publishing and subscribing to events, aka the bulletin board
- Entities post events subscriptions to the bulletin board, and publish events to the bulletin board. The bulletin board infrastructure does all the event management and distribution
If you’ve done any WPF work in the past (or in the present) then you might recognize this style as the Weak Event pattern.
Whilst similar in design to the Hollywood style, this style further decouples the entities with an EventManager that sits between them all.
So let’s start by defining what a handler and event manager looks like:
Unfortunately we have to forfeit some type safety here as we unify different events under the same umbrella. Here’s the implementation for the IEventManager interface:
The 3 entities – DataStorage, StopWordsFilter and WordFrequencyCounter – are similar to those in the Hollywood style, except they now subscribe and publish events through the aforementioned IEventManager abstraction.
Oh, and we’ll stick with the RunArgs type we created last time:
Finally, to put everything together:
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, 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