I believe that I read that Cadence can schedule activities based on many potential ways using task lists, but there´s not much information that expands on this idea and how it can be used.
In particular, this part of the documentation:
While Cadence task lists are queues, they have some differences from commonly used queuing technologies. The main one is that they do not require explicit registration and are created on demand. The number of task lists is not limited. A common use case is to have a task list per worker process and use it to deliver activity tasks to the process. Another use case is to have a task list per pool of workers.
I'm also not clear if every worker needs to support every potential activity sent to a task list, so it would be lovely to see an example of multiple different workers.
I believe that I read that Cadence can schedule activities based on many potential ways using task lists, but there´s not much information that expands on this idea and how it can be used.
In particular, this part of the documentation:
I'm also not clear if every worker needs to support every potential activity sent to a task list, so it would be lovely to see an example of multiple different workers.