does the team plan on integrating step functions in any way within SST? such as a SST-based higher-level construct versus importing a raw CDK step function... i'd like to hear what the team has to say on the choreography vs orchestration aspect of micro services. also interested in seeing how the SST library might package together their higher-level constructs with step functions here's an article that i think is excellent. https://theburningmonk.com/2020/08/choreography-vs-orchestration-in-the-land-of-serverless/

Can't speak on what is on the teams roadmap, but I am using SST with Step Functions. I use the CDK to define the Step Functions, which I find is a pretty good interface. SST has been helpful when using Lambdas in my Step Functions. I simply use the SST Function construct when defining the workflow. I've never tried using other constructs (SQS, Table, etc), but assume they'd work similarly

and you're doing something similar to

Api>Lambda>StepFunction

? where the center lambda is "proxying" the event/payload to your step function, using the SDK within the lambda

In my case, I'm trigger the Step Function via an Event Bridge rule. Event Bridge->Step Function

i think that proxying flow is necessary because there isnt a direct integration between ApiGW/SQS/etc with Step functions... which kinda makes sense based on apiGw/SQS potentially expecting a response back

correct

correct. iTargetable interfaced StepFunction (very similar to lambda)

and you could use Step Functions to go between ApiGW and SQS (or any number of AWS services) without Lambda in-between by doing input/output transformations as needed

right. and those input/output steps are great places to actually do a lot of "error handling" during the orchestration

Yeah, I agree with those takes. I'm not sure what SST could do to improve the Step Function developer experience outside of the live Lambda development environment.

with

sst.Api

ur code is a lot more concise than u were to write CDK code

new Api(stack, "Api", {
  routes: {
    "GET  /notes": "src/list.main",
    "POST /notes": "src/create.main",
    "$default"   : "src/default.main",
  },
});

@Kevin Wright perhaps Event bridge rules + filters combined with event archives could also give you a replay setup even without using step functions