Welcome to the Rube Goldberg Challenge! This solution contains a sample Machine to store an event registration (like when someone signs up for an event). The architecture looks something like this:
The goal in this challenge is to add steps in between the two Lambda handlers, thus increasing it's silliness and decreasing it's efficiency. Why are we doing this again?
Scoring Criteria
- Creativity
- Number of Steps
- Number of Unique Services
- Silliness Factor
- Extravagance
- Inefficiency
Rules
- Steps can be added manually, programmatically, whatever
- You don't have to write code to add steps
- Be kind to one another
- Have fun!
This whole solution is built on AWS SAM and super easy to deploy. Give this recipe a try:
- Launch a Cloud 9 instance, pop into the terminal
- Clone this repo
git clone https://github.com/aulvi/rube-goldberg-challenge.git - Deploy the solution. When this is done it will spit out the RegistrationApi endpoint url, highlight it and copy it for later.
cd rube-goldberg-challenge; sam build && sam deploy --guided - Test it
- Edit
register.shand populate the variables with your own data, including the endpoint url from Step 3. - Run
./register.sh - Go into DynamoDB and see if your registration was saved correctly
- Edit
- Hope that worked!
See the AWS SAM developer guide for an introduction to SAM specification, the SAM CLI, and serverless application concepts.