We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently every persistence has an "At a glance"-section, which states what type of concurrency control is supported.
The SQL persistence section is a bit unclear, as it mentions supporting both, but it's currently not possible to configure. This is clearly stated in the documentation for high-load scenarios for sagas though and in this sample.
It becomes more confusing as the Outbox in SQL persistence supports different concurrency modes. The "at-a-glance" section does define concurrency for sagas only.
Therefore, this issue aims to holistically review the at a glance section regarding concurrency:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently every persistence has an "At a glance"-section, which states what type of concurrency control is supported.
The SQL persistence section is a bit unclear, as it mentions supporting both, but it's currently not possible to configure. This is clearly stated in the documentation for high-load scenarios for sagas though and in this sample.
It becomes more confusing as the Outbox in SQL persistence supports different concurrency modes. The "at-a-glance" section does define concurrency for sagas only.
Therefore, this issue aims to holistically review the at a glance section regarding concurrency:
The text was updated successfully, but these errors were encountered: