Reputation:
We have a lot of jobs that have to run on our local computers, but we want to be able to run and manage those jobs from the cloud. These are not computer-admin type jobs. They are more about business-related tasks.
We have thought seriously about doing this a couple different ways:
We have also looked at a few other ways we might be able to leverage Azure for this kind of thing:
So I'm trying to decide amongst these approaches, or see if there is a better way.
I think I'm going to try the Azure Event Grid approach and get the Hybrid Connection Manager installed on some local machines and then keep some PowerShell scripts running 24/7 to monitor the specified port. Once an event from Azure Event Grid is routed to the Hybrid Connection Manager, it will then route it to the port that PowerShell is listening to and PowerShell can then trigger the job that needs to be run on the local computer.
I really like that approach since I can now connect my local events on my local computer to Azure and third-party events using Azure Event Grid. To me that opens up a world of possibilities for integration amongst disparate systems. But before I take this approach, I want to make sure it is the best one.
Upvotes: 2
Views: 2887
Reputation: 326
It is unclear what type of data you are going to be sending from the cloud. You need to think about
1) Do you want Pull or Push capability to trigger the tasks? I would recommend Pull if you want to carry out maintenance on your local computers. In addition to the fact your local computers have a limited capacity and can’t scale based on a load with Push.
2) Do you want to install additional Server software? Azure Service Bus doesn’t need any Gateway to work on premise.
Azure Service Bus can be implemented with a Windows Service, IIS always on application, it still gives you the flexibility of integrating with 3rd party software as it is can work with Logic Apps, Flow and Azure Functions can be used with Azure Service Bus.
Upvotes: 1