-
Notifications
You must be signed in to change notification settings - Fork 178
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
examples #24
Conversation
examples/2-clicks/README.md
Outdated
### Partitioning and Concurrency | ||
|
||
Messages are partitioned in Kafka using the message key. Messages within each partition are processed sequentially, | ||
but in parallel for all partitions. That means for our case, different users can be modified |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds a bit wonky, maybe something like Messages are processed sequentially inside a given partition but multiple partitions process messages concurrently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
examples/2-clicks/README.md
Outdated
|
||
Messages are partitioned in Kafka using the message key. Messages within each partition are processed sequentially, | ||
but in parallel for all partitions. That means for our case, different users can be modified | ||
in parallel. A single user however is always modified sequentially, because all messages for that user are assigned |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in parallel -> concurrently
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
examples/2-clicks/README.md
Outdated
Messages are partitioned in Kafka using the message key. Messages within each partition are processed sequentially, | ||
but in parallel for all partitions. That means for our case, different users can be modified | ||
in parallel. A single user however is always modified sequentially, because all messages for that user are assigned | ||
to the same partition which runs sequentially. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we should add a small explanation here as to why the messages for the user are assigned to the same partition, ie. Since we are using the user id as the message's key...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
No description provided.