Check out my new course Learn you some Lambda best practice for great good! and learn the best practices for performance, cost, security, resilience, observability and scalability.
Description for today’s challenge is here.
Modelling and simulating a RPG, this challenge totally got my nerd brain into overdrive, which is probably why I went totally overboard with modelling the domain! (you’ll see soon enough..)
First we have characters in the game (you and the boss) with hit points (HP), damage and armor scores:
Then we have the equipments, which have costs, as well as damage and armor stats:
Then we also have shops, who sell these equipments:
Initially, you have 100 Hit Points, but no damage or armor stats (these come from equipments).
The state of the boss comes from your input:
We also need to configure the shop’s inventory according to the description of the challenge:
From the description, we know that:
- you have to pick one weapon
- you can have 0-1 armor
- you can have 0-2 rings
So, to make combining equipments easier later on (we want your selection of equipments to be a simple Equipment), let’s create a few sequences of Equipment to represent your choices of weapons, armors and rings.
For weapons and armors, this is pretty straightforward:
For rings, it’s slightly more involved:
Because the ordering of the rings are not important – [| ring1; ring2 |] is the same as [| ring2; ring1 |] – so here we work out all combinations of 2 rings from the available 6.
Next, let’s work out all possible equipment combinations we can buy from the shop:
We’ll also need to be able to simulate a game between you and the boss:
Notice in the inner recursive loop above, we swap the role of the attacker and defender on every iteration (whilst also deducting the defender’s HP) and return the name of the winner when the defender’s HP reaches 0<HP>.
Now that all the pieces are in place, we can answer the challenge by iterating over all equipment combos, and sending you in battle with the boss with each. For the combos that results in you winning, we simply work out the cost and find the min:
Only a minor tweak is required here – change the winner to “boss” and look for max cost instead of min:
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 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. Enrol now and enjoy a special preorder price of £9.99 (~$13).
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 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