1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.A P I 3 1 3Building production-grade workflow patterns with AWS Step FunctionsEric JohnsonPrincipal Developer A 2025,Amazon Web Services,Inc.or its affiliates.All ri
2、ghts reserved.Who am I?Eric JohnsonPrincipal Developer AdvocateServerless geekFather of fivePreviouslySolutions architectSoftware developerDesignerP 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Meet Tony 2025,Am
3、azon Web Services,Inc.or its affiliates.All rights reserved.Meet Tony 2020:COVID pivot to pizza 2025:80 stores,4.3M orders/year Massive orchestration challenge Lambda spaghetti architecture Breaking point reachedFive years from garage startup to 80-store empire 2025,Amazon Web Services,Inc.or its af
4、filiates.All rights reserved.Tonys first architecture Function-calling-function chains Shared state without coordination Manual orchestration everywhere No error handling or retries Zero visibility into failuresThe Lambda labyrinth that led to Step FunctionsReceiveOrderProcessPaymentCheckForDriverSc
5、heduleDeliverySendConfirmationCheckInventoryValidateOrder 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Edjgeek saysThis is not a Lambda problem,this is an orchestration problem“2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.The solution:AWS Step Functions Vi
6、sual workflow orchestration Built-in error handling and retries Direct AWS service integrations Automatic scaling and monitoring Pay-per-use pricing model 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Step Functi