mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
31 lines
1.5 KiB
ReStructuredText
31 lines
1.5 KiB
ReStructuredText
.. You can adapt this file completely to your liking, but it should at least
|
|
contain the root `toctree` directive.
|
|
|
|
BigchainDB Nodes, Clusters & Federations
|
|
========================================
|
|
|
|
A **BigchainDB node** is a server or set of closely-linked servers running RethinkDB Server, BigchainDB Server, and other BigchainDB-related software. Each node is controlled by one person or organization.
|
|
|
|
A set of BigchainDB nodes can connect to each other to form a **cluster**. Each node in the cluster runs the same software. A cluster contains one logical RethinkDB datastore. A cluster may have additional servers to do things such as cluster monitoring.
|
|
|
|
The people and organizations that run the nodes in a cluster belong to a **federation** (i.e. another organization). A federation must have some sort of governance structure to make decisions. If a cluster is run by a single company, then the federation is just that company.
|
|
|
|
**What's the Difference Between a Cluster and a Federation?**
|
|
|
|
A cluster is just a bunch of connected nodes (computers). A cluster might be operated by just one person. A federation is an organization which has a cluster, and where each node in the cluster has a different operator.
|
|
|
|
Confusingly, we sometimes call a federation's cluster its "federation." You can probably tell what we mean from context.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
node-requirements
|
|
setup-run-node
|
|
running-unit-tests
|
|
configuration
|
|
bigchaindb-cli
|
|
python-server-api-examples
|
|
federation-set-up.md
|
|
deploy-on-aws
|
|
monitoring
|