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

Add QUARKUS-2492: Transaction API #129

Merged
merged 1 commit into from
Jan 25, 2023
Merged

Add QUARKUS-2492: Transaction API #129

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions QUARKUS-2492.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# QUARKUS-2492 - Transaction API

JIRA link: https://issues.redhat.com/browse/QUARKUS-2492

Programmatic distributed JDBC transaction API based on Narayana library

Documentation:
[Narayana Documentation](https://www.narayana.io/)
[Quarkus JTA](https://quarkus.io/guides/transaction#programmatic-approach)

## Scope of the testing
Test development will focus on
- Quarkus JDBC transactions based on programmatic approach
- Quarkus JDBC transactions based on lambda approach
- Verify commons transactions states as "begin", "commit" and "rollback"
- Verify classic and reactive flavors
- Verify several supported semantics such as "DISALLOW_EXISTING", "JOIN_EXISTING", "REQUIRE_NEW", "SUSPEND_EXISTING"

### Impact on test suites and testing automation
We are going to create two new modules (classic and reactive) under SQL/DB folder, in order to develop new JDBC transaction scenarios.
The main idea is to develop a "real scenario" where the transactions are handler in a service layer, rather than in entity level.
This new module is going to increase the compile time, especially in native mode, and is important to run the scenario in
all the platforms, OCP, Baremetal and native mode. I would say that each native compilation could takes about 3 min and then
1 extra minute in order to run the scenario itself. Overall my prediction is that the total amount of time required to run
transaction API scenarios is about 15 min.

## Getting familiar with the feature

Following actions were taken to ensure familiarity:
- Ensure documentation is clear and easy to understand
- Ensure good user experience and simplicity of use
- Review upstream coverage

## Advanced topics for test development

Narayana JTA transaction support several thread semactics such as "DISALLOW_EXISTING", "JOIN_EXISTING", "REQUIRE_NEW", "SUSPEND_EXISTING". Currently we are just covering the default one (requireNew), but would be great in the future to cover the others.

## Contacts

* Tester: Pablo Gonzalez Granados <[email protected]>