Yan Cui
I help clients go faster for less using serverless technologies.
NOTE : read the rest of the series, or check out the source code.
If you enjoy reading these exercises then please buy Crista’s book to support her work.
Following on from the last post, we will look at the Abstract Things style today.
Style 13 – Abstract Things
Constraints
- Larger problem is decomposed into abstract things that make sense for the problem domain
- Each abstract thing is described by what operations the things of that abstraction can do
- Concrete things are then bound to the abstractions
- The rest of the application uses the things not by what they are but by what they do in the abstract
First, let’s define our abstractions:
Unfortunately, after this point the implementation are basically identical to the Things style (except the relevant members in each type is defined as part of the corresponding abstraction rather than as a member of the type):
Finally, remember we need to “use the things not by what they are but what they do in the abstract”, so call the WordFrequencyController via its abstraction:
You can find the source code for this exercise here.
Whenever you’re ready, here are 3 ways I can help you:
- Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game. This is your one-stop shop to level up your serverless skills quickly.
- Do you want to know how to test serverless architectures with a fast dev & test loop? Check out my latest course, Testing Serverless Architectures and learn the smart way to test serverless.
- I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.