Yes the problem here is that, we want to avoid having to ramp up developers on Temporal as they already have the SQS knowledge and we have all of the SQS observability setup for them. So, was wondering if there is a world in which we can mix and match here, such that developers still only have to “know” about SQS, but under the hood it is Temporal that is serving as the engine that determines how and when we process those messages coming into SQS.
It is a similar use case to the one described here where you recently added a response
This could mean that Temporal is not the solution for this, but wanted to make sure we did our due diligence as we have enjoyed playing around with the technology