-
Notifications
You must be signed in to change notification settings - Fork 554
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
Document how to do inter-partition communication #10083
Document how to do inter-partition communication #10083
Conversation
This tries to explain how we want to do inter-partition communication, and why it should be done this way.
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.
The info blocks don't render as intended
docs/developer_handbook.md
Outdated
|
||
As we've seen, the sending partition may send a command many times to another partition. So, the engine must be able to deal with these redundant commands (i.e. commands that are sent many times). To be specific, the engine must process commands received from another partition idempotently. | ||
|
||
:::info |
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 is not rendered correctly (see https://github.com/camunda/zeebe/blob/korthout-doc-interpartition-communication/docs/developer_handbook.md)
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.
Interesting. I've found that GH supports info blocks in the form of block quotes (beta feature that may be subject to change).
That looks like this:
Note
So information, much wow!
There is a discussion ongoing about supporting the :::info\n...\n:::
syntax.
GH markdown syntax now supports info and warning blocks in the form of blockquotes. This is silly because the rest of the internet uses the ::: syntax. But at least this is rendered by GH. See community/community#16925
96833cd
to
dd2d438
Compare
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.
lgtm 🎉
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.
@korthout nice 👍
bors merge |
Build succeeded: |
Description
During our team meeting, we discussed that we wanted to document how we do (and want to do) inter-partition communication.
This is an attempt to document how we want to do inter-partition communication, and why it should be done this way.
Related issues
relates to #10064
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation:
Please refer to our review guidelines.