Multi-Resource/Multi-Vault/Multi-Server Instance ACID Transaction Scopes: scope statement to be added to the Spec

[mwherman2000]

1. The word transaction doesn't appear anywhere in the current specification
2. There needs to some specification of the level or scope of ACID transactions to be supported by an EDV software implementation (https://www.ibm.com/support/knowledgecenter/SSGMCP_5.4.0/product-overview/acid.html).

For example, is transactional integrity guaranteed cross:

1. A change to a single resource in a single physical data vault on a single server instance?
2. A batch of multiple changes to a single resource in a single physical data vault on a single server instance?
3. A batch of multiple changes to multiple resources in a single physical data vault on a single server instance?
4. A batch of multiple changes to multiple resources across multiple physical data vaults on a single server instance?
5. A batch of multiple changes to multiple resources across multiple physical data vaults across multiple server instances?
6. Other combinations of the above...

[mwherman2000]

Here's an EDV Server Instance architecture reference model (ARM) to assist with the above discussion...

[mwherman2000]

In last week's call, it was decided that the version 1 supported transaction scope is:

1. A change to a single resource in a single physical data vault on a single server instance

Implications:

• Multi-user, parallel reads (multi-threaded reads) are permitted.
• All other multi-user, updating actions will block and will be performed as if they were on a running single thread. Reads will block until the updating actions in front of the read have been completed.
• Updates are permitted to a single resource and these single updates (CUD) will be performed with ACID transactional integrity.

This issue can be closed when wording similar to the above appears in the Spec and its approved.

[mwherman2000]

Related issue: https://github.com/decentralized-identity/confidential-storage/issues/194