Implementing a custom Trigger for an Isolated .Net Azure Function
For this post I wanted to research how to implement a custom trigger for Azure Functions running in the isolated process model.
If you are familiar with the Azure Function roadmap, you will know that the in-process model is essentially deprecated, and isolated process is the way forward.
In-Process functions will run the function host and your handler code in the same process, while isolated functions have the host and your user code split into two processes. The payload received by the host is then passed onto the user code process.
From a framework development point of view, this makes it much more simple, since hosting of the user code takes place on a regular .Net application without requiring integration of host and user code on the same process.
However, on the flipside, it is a bit more complicated to actually transfer data from one to the other process (which is done through gRPC).
For this post, I want to implement a custom Redis Stream trigger, but make it work with the new isolated process model.
