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 4 ways I can help you:
- If you want a one-stop shop to help you quickly level up your serverless skills, you should check out my Production-Ready Serverless workshop. Over 20 AWS Heroes & Community Builders have passed through this workshop, plus 1000+ students from the likes of AWS, LEGO, Booking, HBO and Siemens.
- If you want to learn how to test serverless applications without all the pain and hassle, you should check out my latest course, Testing Serverless Architectures.
- If you’re a manager or founder and want to help your team move faster and build better software, then check out my consulting services.
- If you just want to hang out, talk serverless, or ask for help, then you should join my FREE Community.