Thank you for another great video! 😊 It's really interesting to think in a step function first approach. What I think might be challenging is how to reuse and change parts of a system that's based entirely on step functions. One way of course it is to wrap each common flow as a step function and call it from another step function. If you have any more on this topic please share, I'd love to learn more 😊
Hi Marcia, thanks for the video. Do you know if from the aws step function I can execute a map state that is not executed in parallel? I ask you why I need to call an endpoint for all the records of a dynamodb table one at a time
Thank you for another great video! 😊
It's really interesting to think in a step function first approach.
What I think might be challenging is how to reuse and change parts of a system that's based entirely on step functions.
One way of course it is to wrap each common flow as a step function and call it from another step function.
If you have any more on this topic please share, I'd love to learn more 😊
Great idea. I will make more content about step functions for sure
@@foobar_codes Awesome! Thank you 😊
Hi Marcia, thanks for the video. Do you know if from the aws step function I can execute a map state that is not executed in parallel? I ask you why I need to call an endpoint for all the records of a dynamodb table one at a time
you can defeine concurrency in the map state.
@@foobar_codes oh thank you