I have a use case where workflows are started when certain database entries are modified. A unique database entry name is used as a workflow id. These workflows can take a while and new modifications might occur during that time. It is important that the corresponding workflows execute in sequential order. Is there a way to achieve this without resorting to an additional work queue that’s outside of Temporal?
The standard approach is to not start a workflow on each modification but SignalWithStart a workflow with the same entry name about it. This way the workflow can buffer the signals and process them one by one.