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.

Sign up for GitHub

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

Jump to bottom

StageConfig.setReadOnly(), .setNonTransactional() (as well as set[Non]Idempotent(), .setSafe()) #78

Open
stolsvik opened this issue Nov 21, 2022 · 0 comments
Open

StageConfig.setReadOnly(), .setNonTransactional() (as well as set[Non]Idempotent(), .setSafe()) #78

stolsvik opened this issue Nov 21, 2022 · 0 comments
Labels
thoughts Issues describing some thoughts around a subject

Comments

@stolsvik
Copy link
Contributor

Related to #49, where the stage lambda can runtime mark the processing as idempotent etc, it might give room for more optimizations if the entire stage was marked.

  1. If it was ReadOnly, the SQL transaction (and connection?) could be marked as such (ref Spring)
  2. If NonTransactional, neither JMS nor the SQL Connection would be transactional, resulting in speed boost.
@stolsvik stolsvik added the thoughts Issues describing some thoughts around a subject label Nov 21, 2022
@stolsvik stolsvik mentioned this issue Nov 21, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
thoughts Issues describing some thoughts around a subject
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stolsvik