NuoDB components, their relationships, and rules of use.


What are the basic components of NuoDB, their relationships, and rules of use?



TRANSACTION ENGINE (TE) - a process that provides access to a single database. It handles requests from clients, caches data, and coordinates transactions.

STORAGE MANAGER (SM) - a process that provides durability of the data that it handles (for example by writing to disk).

AGENT - a process that manages NuoDB processes running on a particular computer. It starts and stops the NuoDB servers and communicates with the broker about the state of the system.

BROKER - a server that manages access to transaction engines and storage managers. It is the process to which clients first connect. It uses a load-balancing algorithm to establish direct connections between clients and the TEs.

DOMAIN - A domain is a set of hosts provisioned to run NuoDB. A host is provisioned to run NuoDB by starting an agent.

Some basics:

A. EACH server on which you wish to run a Transaction Engine (TE) or Storage Manager (SM) must first be running ONE NuoDB agent.

B. At least one of the agents in a domain must be run as a broker.

C. There may be any number of TEs running on a single machine or across a cluster.

D. There may be any number of SMs running on a single machine or across a cluster.

E. EACH SM stores a complete copy of all data in your database. A 2nd or 3rd SM is only needed for redundancy.


Have more questions? Submit a request


  • Avatar

    I think this a great section to role into the product documentation.

    Originally posted on 2012-08-17 08:38