AWS Step Functions Supports 200 AWS Services To Enable Easier Workflow Automation
aws.amazon.com/blogs/aws/now-aws-step-functio...Posted Oct 1, 2021, 1:21 AM UTC
Posted Oct 1, 2021, 1:21 AM UTC
“In this demo, you are building an application that, when given a video file stored in S3, transcribes it and translates from English to Spanish.”
It’s crazy that this can even be a simple demo on a website to show off some functionality. What a time to be alive.
Is there a way to test these at all or is it kind of manual, hack around in a dev environment then clone to prod?
honestly, I think step functions are a scam, because it's not just lock-in - it's lock in to a language that isn't testable in any meaningful way.
Another commenter noted that learning the arcane input/output syntax is hard. Imagine joining a company where all of their orchestration was managed by unreadable YAML specs that can't be tested unless you can deploy the whole system end to end.
I think Step Functions as a whole is crying out for a Stacker/Terraform/whatever layer that can be written and tested in an actual programming language, and then simply gets "transpiled" to their syntax for deployment.
They are really useful but I do wonder if they're going to end up being the next database stored procedure.
this is a great analogy and I appreciate you bringing it to my attention.
The concept of a stored procedure is great. The practical usage of one is usually that you're massively trading off developer experience and development/testing/maintenance time for the advantage of raw performance. Sometimes this is a great tradeoff, but often it's just cargo-culting performance.
That’s always been my feeling too. Okay thanks for your thoughts. Happy cake day too.
Not to mention the horrible naming ,,,
as an engineer, a "step function" means something very specific to me .. and this is not it
Why AWS
OOoooooh man you tellin me I can CRUD R53 records from step functions now. So many interesting possibilities with all the services opened up.
Wow!
This is absolutely great, I have created so many Lambdas only to do basic AWS API calls. It will be also a good opportunity to really learn how the input/output parsing in Step Functions works.
Agreed. I am super positive about this. I’ve created some really useful workflows with StepFunctions but the Lambda glue required between services was icky.
I’m also less down on the lack of testability than others. I don’t need to test if a boolean switch in a workflow orechestrator works as expected. I don’t write tests to validate the object I put to S3.
For vendor lock-in - if I’m translating/enriching documents stored in s3 using Translate and Comprehend then storing them in a managed DB service...i might as well go all in. If everything i need is in the ecosystem then it’s the type of vendor lockin that brings real business value.
Polling loops for asynch services feel like an anachronism in a managed workflow service though - no reason the orchestrator can’t abstract out that heavy lifting. Well, no reason other than AWS’s inability to develop consistent APIs between services.
Yeah, I hope that polling loop "hey-have-you-finished?" eventually gets abstracted away in SFN too. This happens so damn often, especially when working with AWS AI Services.