Thread by @UdiDahan

Did you know that in #SQS you can only delay the delivery of a message by at most 15 minutes?

docs.aws.amazon.com/AWSSimpleQueue…

If you wanted to use messaging for scheduling business activities overnight, end-of-week, or end-of-month, that can be a problem.

If you're using NServiceBus on top of SQS, we've solved that problem for you. By combining FIFO queues in #AWS with the natural delayed delivery of SQS, and appropriately bouncing messages between them, we can support arbitrarily long times.

Check it out: docs.particular.net/transports/sqs…

Some people have asked me "why not AWS Step Functions instead?"
aws.amazon.com/step-functions/

> AWS Step Functions makes it easy to coordinate the components of distributed applications and microservices using visual workflows.

First of all, the whole visual programming thing... works great for 90% of the cases, terrible for 10%. Version control, unit testing, all the things that matter where larger teams need to deal with a more complex domain.

You might say that AWS Step Functions is the VB6 equivalent to Sagas in NServiceBus, which are properly unit-testable, version-control friendly, object-oriented state machines in code.

Oh, and you still get nice visualization of how the whole thing runs: docs.particular.net/serviceinsight…