Fixing Fullstackbulletin.com part 6 - Twitch Live Stream
1In this sixth session, we fixed an interesting regarding the step function state management for which the `dryRun` configuration made the step function fail when not set. We also started to work on our first Lambda in Rust using Cargo Lambda (https://www.cargo-lambda.info/).
The fix was made by introducing 2 "pass" steps and doing some clever data mapping, also involving AWS Step Functions intrinsic functions (https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-intrinsic-functions.html)
The changes for this fix are available in this PR: https://github.com/FullStackBulletin/sls-create-newsletter-issue/pull/74
We currently have a draft PR for the Rust changes, even though these are currently not fully working: https://github.com/FullStackBulletin/sls-create-newsletter-issue/pull/75
During the stream we also mentioned the following resources:
- https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/building-rust.html
- https://theburningmonk.com/2020/08/choreography-vs-orchestration-in-the-land-of-serverless/
- Rob Pike "Concurrency is not parallelism": https://www.youtube.com/watch?v=oV9rvDllKEg
In the next live streams, we will continue working on this particular lambda function and implement its business logic: scraping a specific web page with the list of published issues and extracting the number of the latest issue (so we can use that to determine the number of the next issue).
You can follow the next live streams at https://twitch.tv/loige
All the code is available at https://github.com/FullStackBulletin
Finally, if you want to subscribe FullStackBulletin, check it out at: https://fullstackbulletin.com/