Which part would you eat?
None? Ok, you are transactional.
Either all is good or nothing.

ACID Transactions

DVTDS offers full support for ACID transactions. At the LDAP interface they are compliant with RFC5805. Similar to transactions in relational databases it guarantees that either all updates of a transaction are executed or none of them (ACID Paradigm - Atomicity, Consistency, Isolation, Duration). This property assures data consistency and removes the burden of complex error handling from client applications. Transaction may be distributed when the data content is spread over several nodes and replica. In such distributed environments the database automatically handles the individual communications across multiple nodes.

Same as for simple multi master replication DVTDS detects distributed conflicts and solves them automatically by means of precedence rules. Either the particular client has higher precedence or the particular request type or the particular target server. In any case the data remains consistent across the entire set of participating nodes. Conflict resolving takes place in real time. In addition the database supports quality of service configuration on a per client basis. This feature can be used to preempt ongoing transactions of low priority clients when clients with higher priority (like real time applications) need to access the same objects.