All geek questions in one place

Azure Service Fabric and Scheduled Tasks

Let's say you have 30+ console applications running on a Windows machine that can be invoked manually or through scheduled Windows tasks , which would be recommended to move / implement them in Service Fabric?

One way to implement this would be a single Service Fabric application with many stateless services ( Reliable Actorusing timers / reminders), each of which will listen on the service bus queue / topic, and then use the Azure Scheduler to send messages to the queue / topic.

What are the pros and cons of such an implementation? This article seems to list a few of them .

What would be other ways to implement this?

It seems like some people are trying to uphold the inclusion of pub / sub framework in the Service Fabric, if this becomes part of the Service Fabric, will this be a valid option?

+4
source share
2 answers

I would look at the use of Azure functions, it would be great for simplicity and it would be fashionable to be serverless computing, that is, you would not need to unwind and configure the bus or queue, and then use the reliable Stateless APIs and call the Azure time function without a public service.

See here for a start:

https://azure.microsoft.com/en-us/services/functions/

db - , HTTP-.

Video

+3

. Service Bus Azure Scheduler.

, API . / , / ( concurrency). , , - .

, , , , Service Fabric .

+3

Source: https://habr.com/ru/post/1654486/

More articles:


All Articles