- Although I started using
slash-create, which does explicitly support AWS Lambda, I stopped using it because:- I needed to load data asynchronously before registering the commands, as I needed to work out different options. This isn't possible with
slash-create - I needed to have multiple lambda entry points, which doesn't particularly work with it either
- I needed to load data asynchronously before registering the commands, as I needed to work out different options. This isn't possible with
- The state machine setup was used because we need to be able to defer, but then perform another response. For more discussion see this issue.