NuoDB At a Glance

NuoDB is a distributed cloud database management system with a rich SQL implementation and full support for transactions. NuoDB is designed to offer:

  • Scale-Out Performance

  • Continuous Availability

  • ANSI-Standard SQL

  • ACID compliance

  • Region Distribution

  • Multi-Tenancy

  • No-Knobs Administration

As a distributed system, a NuoDB installation consists of a collection of hosts, called a domain, that have been provisioned to work together to support one or more NuoDB databases. One or more instances of the following kinds of NuoDB processes are running on the hosts in the domain:

  • Admin process (AP): Manages SQL application access to transaction engines. The AP is independent of any particular database in the NuoDB system. A domain comprises one or more APs. There is never more than one AP on a host.

  • Transaction Engine (TE): Provides application access to a single NuoDB database by processing SQL commands, caching data, and coordinating transactions with other TEs and storage managers (see below).

  • Storage Manager (SM): Reads and writes transacted data to and from disk.

Applications use JDBC or other interfaces to connect to TEs. TEs and SMs communicate with each other as required to implement transactions, durability, and the other ACID behavior expected from a full SQL database.

Regarding how a client connects to a simple NuoDB database system, the steps in the process are as follows:

  1. An application that seeks to connect to the database calls to the AP on host A. Because the AP communicates with all APs in the domain it has a record of which TEs are available and it uses that information to determine the best TE for the application.

  2. The AP communicates to the client that it should connect to the TE on a second host. After that, the application no longer communicates with the AP.

  3. The client connects to the transaction engine on the second host.

A domain may consist of multiple TEs and multiple SMs, configured as necessary to support scalability, availability, or redundancy requirements. A minimal deployment of NuoDB consists of a single TE, but that configuration provides no durability. A minimal durable configuration consists of a single TE and a single SM. A minimally-redundant configuration consists of two TEs and two SMs, paired to two hosts.

Interested in learning more? Here are some options: