doozerd

GitHub describes it as A consistent distributed data store.. The repository metadata lists Go as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

GitHub describes it as A consistent distributed data store.. The repository metadata lists Go as its primary language. The metadata lists the MIT license. The README describes the project this way: Doozer is a highly-available, completely consistent store for small amounts of extremely important data. When the data changes, it can notify connected clients immediately (no polling), making it ideal for infrequently-updated data for which clients want real-time updates. Doozer is good for name service, database master elections, and configuration data shared between several machines. See When Should I Use It? , below, for details.

The README section "Quick Start" states: 1. Download doozerd 2. Unpack the archive and put doozerd in your PATH 3. Repeat for doozer 4. Start a doozerd with a WebView listening on :8080

The README section "How Does It Work?" states: Doozer is a network service. A handful of machines (usually three, five, or seven) each run one doozer server process. These processes communicate with each other using a standard fully-consistent distributed consensus algorithm. Clients dial in to one or more of the doozer servers, issue commands, such as GET, SET, and WATCH, and receive responses.

The README section "How Does It Work?" states: Each doozerd process has a complete copy of the datastore and serves both read and write requests; there is no distinguished "master" or "leader". Doozer is designed to store data that fits entirely in memory; it never writes data to permanent files. A separate tool provides durable storage for backup and recovery.

The repository README is the source for this review. It does not replace a local installation or an independent test.

• Source 1 · Project repository
• Source 2 · README