Explore >> Select a destination
|
You are here 
|
tlakomy.com | ||
| | | | |
states-language.net
|
|
| | | | | ||
| | | | |
blog.kochie.io
|
|
| | | | | Building your own compute cluster is hard, so let's just use lambda functions instead. | |
| | | | |
sigpwned.com
|
|
| | | | | I'm using AWS Step Functions to do some complex orchestration of services that could span more than 25,000 state transitions and exchange data sets larger than 256KB, so I'm making heavy use of the new distributed map feature. It definitely makes things easier than the old everything-is-a-child-execution approach! However, the ResultWriter field is not particularly | |
| | | | |
thinkingeek.com
|
|
| | | AWS Lambda is one of those technologies that makes the distinction between infrastructure and application code quite blurry. There are many frameworks out there, some of them quite popular, such as AWS Amplify and the Serverless Framework, which will allow you to define your Lambda, your application code, and will provide tools that will package and provision, and then deploy those Lambdas (using CloudFormation under the hood). They also provide tools to locally run the functions for local testing, which... | ||
