Oracle NOSQL services network requests to store and retrieve data which is organized into key-value pairs.
The typical application is a web application which is servicing requests across the traditional three-tier architecture: web server, application server and NOSQL DB.
An application makes use of Oracle NoSQL Database by performing network requests against Oracle NoSQL Database's key-value store, which is referred to as the KVStore.
The requests are made using the Oracle NoSQL Database Driver, which is linked into your application as a Java library (.jar file), and then accessed using a series of Java APIs.
By using the Oracle NoSQL Database APIs, the developer is able to perform create, read, update and delete operations on the data contained in the KVStore
Oracle NoSQL Database is tested using Java 7.
Key Value Store (KV Store):
The KVStore is a collection of Storage Nodes which host a set of Replication Nodes. Data is spread across the Replication Nodes. The store contains multiple Storage Nodes.
A Storage Node is a physical (or virtual) machine with its own local storage. The machine is intended to be commodity hardware. It should be, but is not required to be, identical to all other Storage Nodes within the store.
Replication Nodes and Shards
A Replication Node can be thought of as a single database which contains key-value pairs.
Replication Nodes are organized into shards. A shard contains a single Replication Node, called the master node, which is responsible for performing database writes.
The master node copies those writes to the other Replication Nodes in the shard, called the replicas.
These replicas obtain a full copy of the data from the corresponding master node and are used to service read-only operations. Although there can be only one master node at any given time, any of the members of the shard are capable of becoming a master node.
Note:
The more shards that your store contains, the better your write performance is because the store contains more nodes that are responsible for servicing write requests.
Replication Factor
The number of nodes belonging to a shard is called its Replication Factor.
The larger a shard's Replication Factor, the faster its read throughput (because there are more machines to service the read requests) but the slower its write performance (because there are more machines to which writes must be copied).
The typical application is a web application which is servicing requests across the traditional three-tier architecture: web server, application server and NOSQL DB.
An application makes use of Oracle NoSQL Database by performing network requests against Oracle NoSQL Database's key-value store, which is referred to as the KVStore.
The requests are made using the Oracle NoSQL Database Driver, which is linked into your application as a Java library (.jar file), and then accessed using a series of Java APIs.
By using the Oracle NoSQL Database APIs, the developer is able to perform create, read, update and delete operations on the data contained in the KVStore
Oracle NoSQL Database is tested using Java 7.
Key Value Store (KV Store):
The KVStore is a collection of Storage Nodes which host a set of Replication Nodes. Data is spread across the Replication Nodes. The store contains multiple Storage Nodes.
A Storage Node is a physical (or virtual) machine with its own local storage. The machine is intended to be commodity hardware. It should be, but is not required to be, identical to all other Storage Nodes within the store.
Replication Nodes and Shards
A Replication Node can be thought of as a single database which contains key-value pairs.
Replication Nodes are organized into shards. A shard contains a single Replication Node, called the master node, which is responsible for performing database writes.
The master node copies those writes to the other Replication Nodes in the shard, called the replicas.
These replicas obtain a full copy of the data from the corresponding master node and are used to service read-only operations. Although there can be only one master node at any given time, any of the members of the shard are capable of becoming a master node.
Note:
The more shards that your store contains, the better your write performance is because the store contains more nodes that are responsible for servicing write requests.
Replication Factor
The number of nodes belonging to a shard is called its Replication Factor.
The larger a shard's Replication Factor, the faster its read throughput (because there are more machines to service the read requests) but the slower its write performance (because there are more machines to which writes must be copied).
No comments:
Post a Comment