AWS re:Invent 2023 - Advanced serverless workflow patterns and best practices (API401)

[@pemessh]

The talk should have been named: "Serverless step function workflow patterns and best practices" in my opinion.

[@bls20]

Because it wasn’t advanced or because it’s not clear that it’ll be all about step functions ?

[@loganboyd]

Invent and Simplify!!! Great job

[@AWSEventsChannel]

Thank you. 🙌

[@hellaren]

Thanks for the fantastic presentation!

[@AWSEventsChannel]

🙌

[@andreadiotallevi5780]

Wow this was excellent with some great insights!

[@amazonwebservices]

That's AWSome to hear! 😀 🙌

[@jackfrosch]

Really enjoyed the talk, maybe the one I enjoyed most of all the 2023 re:Invent talks. Did not enjoy hearing someone say EC2 is in a "serverless event-driven pyramid" of managed services unless he was talking in the context of Fargate. However, step functions service is a fantastic serverless offering.

[@bls20]

Hello, speaker here. Glad you enjoyed the talk. The point i was trying to illustrate was not that EC2 is serverless but that it is not a very managed service.

[@daveboyne]

I know this guy! Nice talk Ben 🚀

[@ChrisShenton]

@7:50 "Done." :-) Fantastic.

[@ChrisShenton]

More seriously: this is a GREAT presentation, highlighting some of StepFunctions' super-powers. I love that it can now invoke many many AWS services without need for Lambda intermediaries.

[@amazonwebservices]

That's AWSome to hear! 😀 🙌

[@erizonencina4917]

Hi everywhere, do you think that clean arquitectures could alive with this workflow pattern?. I think that work with step functions is other way to handle application logic, and this seems to be much better handled by code in some language, at least for someone with a few years with aws.

[@bls20]

Unsure what you are asking, can you reword perhaps ?

[@erizonencina4917]

Hello @bls20 thanks for your time, I refer to, could this pattern works with hexagonal architecture? is hexagonal architecture good when we work with serverless functions?

[@enderex]

Hello from the future👋