Hi everyone,
I’m currently struggeling with my use-case scenario.
My application (c# / dotnet core) displays widgets which represents currently waiting “human tasks” in my workflow model. So far I’m using the REST Api via Nuget-Package (Camunda.Api.Client). So even no Java tasklistener coding is required.
Everything works well except the usecase scenario where new “human tasks” should be displayed via Websocket (SignalR) without refreshing the page. So far I read about 3 possible scenarios:
-
Using the plugin “camunda-bpm-reactor” to write a tasklistener (for tasks of type “human task”) to send the taskinformation via message actively to a rest api of my backend → drawback: no middleware / no failover etc.
-
Using the plugin “camunda-bpm-reactor” to write a tasklistener (for tasks of type “human task”) to send the taskinformation to kafka or any other eventbus → drawback: whole middleware setup is needed for just one scenario
-
Using zeebee and listen to tasks with c# client → drawback change all my task types “human tasks” to “service tasks” / whole zeebee setup (which is new to me)
My question to you folks would be if there is any other option (maybe more trivial) that you could think of or is any of my option not desireable ?
Thanks in advance,
Björn