YY
You also may use different process which will generate some message about changes and pass it to target process.
Size: a a a
2020 April 20
SR
Since that service task is a pub sub event, if i am creating new processinstance for every input, then there will be many process instances created.
SR
do it outside the camunda
Can you please elaborate @Kotskin
DK
Satya Ram
Since that service task is a pub sub event, if i am creating new processinstance for every input, then there will be many process instances created.
what kind of messages you want proceed?
DK
process must possobility to be ended, or you will have issues with DB
SR
The use case is, i will be getting sensor data into my service task every 10 seconds, and i am storing the message as process variables, once that is done, i have a dmn where i am trying to compare the threshold with the actual sensor values and then i am calling a call activity, where i will be making an api, if all my conditions inside a dmn are satisfied
DK
and why you want use camunda for that? :)
DK
sensors it a lot of data, you need something more strangeforward like apache storm or kafka streams
DK
becouse camunda relay on RDMS you will get pain in your back soon, if will try to camunda for that use case
SR
Cuz it has dmn, i can check if sensor values are matching with the threshold, if the sensor values are matching my threshold values for 4 minutes, then i would give the user a recommendation which is again inside dmn. If we doing it via rest call for event generation, its more of a manual process.
SR
Since camunda will automate this process of event generation
SR
I want to use camunda
SR
Since my process variables will be replaced whenever a new data comes in
SR
Do you think it will create problem with db
YY
Each variable change means work with db. So, I think yes.
YY
Moreover, each access to variable.
YY
Do sensors send data to you? Or you should pull it?
SR
They send it and we actually subscribe to the topic to which the mqtt is publishing