Skip to content

Commit c9594f1

Browse files
AUTO: Sync ScalarDB docs in English to docs site repo (#1160)
Co-authored-by: josh-wong <[email protected]>
1 parent 5644bff commit c9594f1

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

versioned_docs/version-3.14/two-phase-commit-transactions.mdx

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,15 @@ When using the [Consensus Commit](configurations.mdx#use-consensus-commit-direct
198198

199199
### Execute a transaction by using multiple transaction manager instances
200200

201-
By using the APIs described above, you can execute a transaction by using multiple transaction manager instances as follows:
201+
By using the APIs described above, you can execute a transaction by using multiple transaction manager instances. The following is an example of how that works.
202+
203+
:::warning
204+
205+
The following sample code is a simplified version that solely illustrates how to use the two-phase commit interface and doesn't represent a real-world use case. In actual applications, it is assumed that a transaction manager instance is created per process or service.
206+
207+
For a real-world example, see the [microservice transactions sample tutorial](scalardb-samples/microservice-transaction-sample/README.mdx).
208+
209+
:::
202210

203211
```java
204212
TransactionFactory factory1 =

0 commit comments

Comments
 (0)