Since our handler function is so simple, let's take a look at the application code to see what exactly is going on. Our coffee cupping API is fairly simple and only handles a single resource type at this point, a coffee cupping session object. Before moving forward, it's helpful to take a look at the shape of this resource type:
{ "name": "Cupping session for Serverless Patterns", "formName": "Modified SCAA", "cuppings": [ { "name": "Guatemala Huehuetenango", "overallScore": "85.5", "scores": { "Aroma": 8.6, "Body": 8, "Flavor": 10 }, "notes": "This was pretty good", "descriptors": ["woody", "berries"] }, { "name": "Ethiopia Yirgacheffe", "overallScore": "90", "scores": { "Aroma": 8.6, "Body": 8, "Flavor": 10 }, "notes": ...
