MarkLogic’s XA Transactions feature lets you execute one unified ACID transaction between MarkLogic and another database system. In compliance with the eXtended Architecture standard by The Open Group, MarkLogic’s XA transactions guarantee that MarkLogic’s ACID properties are maintained for transactional updates or are fully rolled back to the prior state.

The XCC API includes support for registering MarkLogic as an XA Transaction Resource Manager. When MarkLogic acts as a Resource Manager, requests submitted to MarkLogic are always part of a multi-statement update transaction.

You can explore some of the technical resources below that explain how XA transactions in MarkLogic work.

Learn More

Participating in XA Transactions

Read how MarkLogic Server can participate in distributed transactions by acting as a Resource Manager in an XA/JTA transaction.

XCC Developer's Guide

Read the guide that provides background on XCC and an overview of what it is, along with API and other documentation, and additional XCC MarkLogic Server Requirements.

Data Consistency Across Disparate Databases

Find out how XA Transactions lets you execute one unified ACID transaction between MarkLogic and another database system.

This website uses cookies.

By continuing to use this website you are giving consent to cookies being used in accordance with the MarkLogic Privacy Statement.