states and Vaults in the R3 Corda storage aspect, each node in the network maintains a vault and it is really a database that tracks all the data that node is privative, so it has all the current and historic states for that node and different nodes can actually have different views of state information.
So there could be data that is shared between three parties only those three will hold it there could be other data that is held by just two of them only those two hold it the third party does not hold it.
So these vaults are currently based on H2 embedded sequel engines and they are also planning to support JDBC have not looked recently whether they have actually added that but I believe they can support any relational database.
The current state of the ledger comprises all the unconsumed transactions. So it is very similar to UTXO. so you can have a sequence of these transactions the rest of it is historic state Corda allows for fine-grained access control on the state sequence.
So I can say who gets access to which state information I can do that in a fine-grained manner.
fabrics in contrast allow this data partitioning through the notion of channels and collections in Corda just the way the message passing works and how the transactions are shared.
Gives you a very strong notion of privacy only the participants of the transaction will ever see the transaction and the data within it.
states and vaults in r3 corda
READ MORE