| Interface | Description |
|---|---|
| BucketManager |
Interface used to interact with the persistence context to
KeyValueEntity
The BucketManager API is used to create and remove persistent KeyValueEntity. |
| BucketManagerFactory |
BucketManager factory. |
| KeyValueConfiguration |
The diana configuration to create a
BucketManagerFactory |
| KeyValueEntity |
A bucket unit, it's a tuple that contains key its respective value.
|
| KeyValueEntity.KeyValueEntityProvider |
A provider of
KeyValueEntity where it will return from two values where the first one is the key
and the second one is the value of the entity. |
| KeyValuePreparedStatement | |
| KeyValueQueryParser |
A query parser to key-value database type, this class will convert a String to an operation in
BucketManager. |
Key-value (KV) stores use the associative array (also known as a map or dictionary) as their fundamental data model. In this model, data is represented as a collection of key-value pairs, such that each possible key appears at most once in the collection. The key-value model is one of the simplest non-trivial data models, and richer data models are often implemented as an extension of it. The key-value model can be extended to a discretely ordered model that maintains keys in lexicographic order. This extension is computationally powerful, in that it can efficiently retrieve selective key ranges. Key-value stores can use consistency models ranging from eventual consistency to serializability. Some databases support ordering of keys. There are various hardware implementations, and some users maintain data in memory (RAM), while others employ solid-state drives or rotating disks.
Copyright © 2017–2019 Eclipse Foundation. All rights reserved.