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

Messaging: design transaction instrumentation #264

Open
lmolkova opened this issue Aug 16, 2023 · 1 comment
Open

Messaging: design transaction instrumentation #264

lmolkova opened this issue Aug 16, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@lmolkova
Copy link
Contributor

#163 (comment)

Many messaging systems support transactional publish and settlement, but the spec does not provide any guidance on how to instrument them

@lmolkova lmolkova added the enhancement New feature or request label Aug 16, 2023
@lmolkova
Copy link
Contributor Author

For example, in Azure Service Bus transactions do not directly affect operation flow. User initiates a transaction, then performs each operation as usual, but with additional transaction context, and then, when the transaction is committed, broker performs all the operations.

image

I.e. for the Azure ServiceBus, we'd be looking for one extra attribute to represent transaction Id.

More investigation is needed for popular messaging systems to see if any general solution could/should be implemented.

@github-actions github-actions bot added the Stale label Feb 15, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 25, 2024
@lmolkova lmolkova reopened this Feb 25, 2024
@lmolkova lmolkova removed the Stale label Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Post-stability
Development

No branches or pull requests

2 participants