0
votes

I am aware that an Azure function app offers a variety of ways its functions can be triggered. Among this is a the Azure storage queue trigger.

I need to use this exact method in my on-premise .NET Core 3.1 Web API project, which until now is exclusively triggered by http requests.

Can this be done?

Cheers

1
You could have an Azure Function that gets triggered by the Azure Storage Queue trigger, and this Azure Function could then call your on-premise Web API endpoint - marc_s
True, although then I have to deal with an on-premise data gateway and firewall configuration, which I wanted to avoid. Should have stated this in my question, sorry. - baouss
I guess one approximation would be to manually check for queue entries every x seconds... - baouss
You can actually run Azure Functions including the triggers on-prem as well, using KEDA: docs.microsoft.com/en-us/azure/azure-functions/… - silent
Thank you. That on the other hand would require docker to be running on the server which is not the case, and tbh I don't think that there ever will. I really had hoped for something I could leverage in an dotnet core app, e.g. with the worker service, or something like that - baouss

1 Answers

1
votes

While I haven't really tried this out before, I believe you should be able to run the Azure Functions Host locally similar to how it runs inside its docker container.

Another option would be to use the WebJobs SDK (on top of which Azure Functions is built) which you should be able to use (along with all available functions bindings) to create a standalone service that you can run on-premise.