Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task lists sample #28

Open
Redundancy opened this issue Sep 20, 2019 · 1 comment
Open

Task lists sample #28

Redundancy opened this issue Sep 20, 2019 · 1 comment

Comments

@Redundancy
Copy link

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.

@mfateev
Copy link
Contributor

mfateev commented Sep 20, 2019

Currently the only example that uses multiple task lists is fileprocessing.

Feel free to join Cadence Slack channel to discuss your use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants