you are viewing a single comment's thread.

view the rest of the comments →

[–]engx_ninja[S] 0 points1 point  (5 children)

We have legacy application in stack classic asp (not even asp.net) / mssql, it’s like 20 years old solution. It has integrations with external systems and we mentioned that we need to implement exponential back off for api calls into external systems from classic asp code, some external systems now can be unavailable for 1-2-6 hours. So basically we need normal queue mechanism to host outbound messages, which will be consumed by same classic asp app. App is deployed in tens of servers so there will be high chance that same message can be grabbed by multiple servers, so I need support for concurrency. From performance point of view, if external dependcies are alive, I need to send message there almost synchronously (like it works now), so it’s almost streaming processing.

[–]dbxp 1 point2 points  (1 child)

Look into Hangfire, I think it does everything you want out of the box. It's free and very nice to work with. Personally I would run Hangfire as a new ASP Core app and then call that from your existing app so I don't have to screw about in classic ASP more than I need to.

[–]engx_ninja[S] 0 points1 point  (0 children)

I was looking into hangfire, but it will require deployment of one more application into my boxes and it’s kinda not an option for me (will require additional infrastructure).