Description for today’s challenge is here.
Another nice and simple challenge whose solution fits nicely into 20 lines, so here goes:
If you have been following this series of posts on this blog, then you’ll have seen something similar to this code in previous challenges already. Couple of subtle points to note here:
- we only yield a combination if the total volume of the containers matches the total (could have done the filtering after the fact, AFAIK there’s no significant performance difference in both approaches);
- we’re using a depth-first approach here – yield the combinations without the current container first, then only yield combinations with this container if it wouldn’t take us over the 150 litre limit
The combination-finding code stays the same, we just need to filter the combos after the fact by length:
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