If you enjoy reading these exercises then please buy Crista’s book to support her work.
Style 10 – Things
You may also know this style as OOP.
- Larger problem is decomposed into things that make sense for the problem domain
- Each thing is a capsule of data that exposes procedures to the rest of the world
- Data is never accessed directly, only through these procedures
- Capsules can re-appropriate procedures defined in other capsules
First, we have a thing for storing data from a file:
Then, we another thing for storing the stop words we’ll dealing with later:
Next, we have another thing that keeps track of the word frequencies:
Finally, we have a thing that controls the flow of our application:
And to tie everything together, we need to construct and run the controller:
You can find the source code for this exercise here.
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.
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