You can become a serverless blackbelt. Enrol in my course Learn you some Lambda best practice for great good! and learn best practices for performance, cost, security, resilience, observability and scalability. By the end of this course, you should be able to make informed decisions on which AWS service to use with Lambda and how to build highly scalable, resilient and cost efficient serverless applications.
If you enjoy reading these exercises then please buy Crista’s book to support her work.
Style 20 – Constructivist
- Every single procedure and function checks the sanity of its arguments and either returns something sensible when the arguments are unreasonable or assigns them reasonable values.
- All code blocks check for possible errors and escape the block when things go wrong, setting the state to something reasonable.
So far we have neglected error handling on purpose, but not anymore. The next few styles will focus on error handling and illustrate the subtle differences between a few different strategies.
In today’s style, we’ll be mindful of errors but provide sensible fallback values wherever possible so that the program can continue.
Take the extractWords function below as an example, when we’re given invalid input we return a sensible fallback value (in this case the empty array) instead of throwing an exception.
Similarly, if we’re not able to open the input file (perhaps the file doesn’t exist), rather than throwing an exception and terminating the program flow, we return an empty array instead so the program may continue.
We’ll apply the same approach to dealing with anomalies in the removeStopWords function here. If we are unable to read the file with all the stop words for whatever reason, we’ll return the input words in its entirety as if the stop words file was empty.
And the same goes to the other functions.
Finally, we string everything together in a pipeline.
When applied well, the Constructivist style to dealing with errors can have a positive impact to user experience in user experience.
For example, browsers take a very Constructivist approach to rendering HTML pages – it’ll do the best job it can even when images, css, js scripts or other resources the page depends on is missing.
Similarly, Netflix’s Hystrix library has a built-in support for fallback commands so that you can gracefully degrade the user experience during exceptional circumstances.
For example, when you execute a HystrixCommand to load the movie list for a user:
- try to load movie list based on user profile (preferences, watch history, etc.)
- UserProfile service is non-responsive
- fallback to fetch generic movie list for UK
- generic movie list for UK not available due to DB outage
- fallback to hardcoded movie list from the service’s config file
which is a whole lot better than the whole app crashing whenever any of the dependent services is not responsive! (apparently that’s how things were at Netflix in the early days)
On the other hand, when you give fallback values to the user without notifying them it can also cause a lot of confusion.
For example, if I had a typo in the path to the stop words file, this will be the output of my program:
the – 4507
to – 4243
of – 3728
and – 3658
her – 2225
i – 2070
a – 2012
which would not be what I was expecting.
Fortunately, in this case we do inform the user of the error so that they’re able to reason about the unexpected output from the program.
We could have done better though, by informing the user that “due to error opening the stop words file, all words from the input file will be counted”.
There are many other situations where an explicit error might be better. A few of the JS examples from Gary Bernhardt’s WAT talk springs to mind!
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 podcast Real-World Serverless where I talk with engineers who are building amazing things with serverless technologies and discuss the real-world use cases and challenges they face. If you’re interested in what people are actually doing with serverless and what it’s really like to be working with serverless day-to-day, then this is the podcast for you.
Check out my new course, Learn you some Lambda best practice for great good! In this course, you will learn best practices for working with AWS Lambda in terms of performance, cost, security, scalability, resilience and observability. We will also cover latest features from re:Invent 2019 such as Provisioned Concurrency and Lambda Destinations. Enrol now and start learning!
Check out my video 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. There is something for everyone from beginners to more advanced users looking for design patterns and best practices. Enrol now and start learning!
Are you working with Serverless and looking for expert training to level-up your skills? Or are you looking for a solid foundation to start from? Look no further, register for my Production-Ready Serverless workshop to learn how to build production-grade Serverless applications!
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 wrong about serverless and vendor lock-in
- You are thinking about serverless costs all wrong
- Just how expensive is the full AWS SDK?
- Many faced threats to Serverless security
- We can do better than percentile latencies
- 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
- Top 10 Serverless framework best practices