@theburningmonk There is no cost advantage with my suggestion over option 1, except if you have some time outs you don’t care about and can’t filter out, but that seems unlikely.
@theburningmonk Cost wise I assumed a ddb item with a stream and lambda invoked only on timeout is going to cost less than an extra standard step function that is always executed.
@theburningmonk The step function can delete the record, which is a different type of item the steam consumer can ignore. But you are right that the stream consumer should check to see if it’s still running, so the ddb item should be the step function execution id.
@theburningmonk Not sure this is better, but you could have an item in DynamoDB TTL and capture the service delete on the stream? Like having another state machine do this, it feels like we are duplicating state management, but this way might be more cost effective.
@ProfPCDoherty How do you appeal to the far right without appearing to support far right policies? Create another party that will not win seats but sends all preferences to you.