A cluster consistency platform
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update PULL_REQUEST_TEMPLATE.md (#1037) Dec 4, 2017
.mvn/wrapper Parallel testing in travis (#1569) Nov 29, 2018
.travis_scripts Parallel testing in travis (#1569) Nov 29, 2018
annotationProcessor Changed version to 0.2.2 (#1456) Aug 17, 2018
annotations Changed version to 0.2.2 (#1456) Aug 17, 2018
bin adding remove node cmdlet (#1227) Mar 26, 2018
cmdlets Changed version to 0.2.2 (#1456) Aug 17, 2018
corfu_scripts Correctly seal servers on epoch change (#1545) Nov 13, 2018
debian Changed version to 0.2.2 (#1456) Aug 17, 2018
docs Describe the Node ID format (#1069) Dec 15, 2017
format Changed version to 0.2.2 (#1456) Aug 17, 2018
generator Validate User Defined Timestamps (#1567) Dec 11, 2018
infrastructure Prevent jitter by increasing sleep for failure detection (#1638) Jan 15, 2019
it Optimize docker image build in it module (#1617) Dec 14, 2018
migration Changed version to 0.2.2 (#1456) Aug 17, 2018
resources updated illustrations Dec 23, 2015
runtime Remove Sparse Trimming Logic (#1632) Jan 9, 2019
samples TransactionBuilder Cleanup (#1594) Dec 8, 2018
scripts Adding JMX MBean dumper (#1252) Apr 9, 2018
test Prevent jitter by increasing sleep for failure detection (#1638) Jan 15, 2019
.gitattributes Distributed log initial version. Sep 19, 2013
.gitignore Creating testing framework (#1460) Oct 15, 2018
.travis.yml Fix: maven verify doesn't work in parallel mode (#1605) Dec 10, 2018
Dockerfile Fixing renamed jar in Dockerfile Jun 15, 2017
LICENSE.txt cleanups Jan 14, 2015
README.md [Readme] fix typo (#1351) Jul 22, 2018
Security.md Fix file path typos in password demo Feb 14, 2017
TestingFramework.md explain the concurrecy test framework Dec 19, 2016
checks.xml Creating testing framework (#1460) Oct 15, 2018
mvnw Parallel testing in travis (#1569) Nov 29, 2018
mvnw.cmd Parallel testing in travis (#1569) Nov 29, 2018
pom.xml Upgrade the Google Guava's Version (#1606) Dec 9, 2018
private.key.enc misisng files Jan 29, 2016
public.key misisng files Jan 29, 2016
test_checks.xml remove magic numbers in tests and enforce style checks Dec 9, 2016



Join the chat at https://gitter.im/CorfuDB/CorfuDB

Build Status codecov

Corfu is a consistency platform designed around the abstraction of a shared log. CorfuDB objects are in-memory, highly available data structures providing linearizable read/write operations and strictly serializable transactions. CorfuDB is based on peer-reviewed research, see References.

Check the Corfu Wiki for a detailed overview of the software architecture and example usage.

Table of Contents

System Requirements

Corfu Basics

Corfu Quick Start

Developing with Corfu

What do I need to run Corfu?

The Corfu infrastructure can run on any system which has Java 8 support. We do not impose any requirements on the kind of storage used - Corfu works with any device that your operating system will allow Java to work with: traditional hard disks, SSDs, and even NVM. We also provide an in-memory mode for nodes which do not require persistence.

Even though Corfu is a distributed system, you can start working with Corfu using just a single machine. In addition, you can easily simulate a distributed Corfu system on a single machine using just a few commands.

So how does Corfu work?

Corfu is built upon the abstraction of a distributed shared log. The Corfu infrastructure provides this log to clients, which use the log for coordination, communication and storage. The log is a highly available, dynamic and high performance scalable fabric: it is resilient to failures and can be reconfigured at any time.

The Corfu infrastructure consists of three components: a layout server, which helps Corfu clients locate the rest of the Corfu infrastructure, a sequencer server, which is used to order updates to the log, and a log server, which stores updates to the log. At minimum a Corfu infrastructure must have one of each server type, but for scalability and high availability a real-world deployment will have many. An administrator need not worry about installing each role separately as they are provided as a single monolithic binary.

Corfu clients interact with the infrastructure through the Corfu runtime. The runtime is currently only available in Java, but we plan on providing it in several other languages in the future. Given the address to a layout server in a Corfu infrastructure, the runtime enables clients to access distributed high-level data structures as if they were local data structures. We provide a mechanism to automatically distribute most Java objects as well.

For more details on the inner workings of Corfu, see the Corfu wiki.

Ok, great - get me started running Corfu!

There are currently two ways to run Corfu - by building the development sources, or on Debian-based systems, installing the corfu-server package. We'll describe how to build Corfu from the development sources first. If you just want to install the Debian package, skip here.

Install From Debian Package

We currently host an apt repository for Ubuntu 14.04 LTS (Trusty). To install Corfu via apt-get, run the following commands:

# Install the package for add-apt-repository
$ sudo apt-get install python-software-properties
# Add the Corfu signing key to your keychain
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 482CD4B4
# Add the Corfu repository
$ sudo apt-add-repository "deb https://raw.github.com/CorfuDB/Corfu-Repos/debian/ trusty main"
# Update packages and install the Corfu server infrastructure
$ sudo apt-get update
$ sudo apt-get install corfu-server

Building Corfu From Source

To build Corfu, you will need the Java JDK 8 as well as Apache Maven 3.3 or later to invoke the build system.

On Linux (Debian/Ubuntu), run:

$ sudo add-apt-repository ppa:webupd8team/java
$ sudo apt-get update
$ sudo apt-get install oracle-java8-installer

Your major release number of Debian/Ubuntu will determine whether the simple command below is sufficient to install Maven 3.3 or later.

$ sudo apt-get install maven

Use the command mvn --version to confirm that Maven 3.3 or later is installed. If an older version is installed, then use the instructions at Installing maven 3.3 on Ubuntu to install manually. PLEASE NOTE: Please substitute the version number 3.3.9 in place of this blog's instructions for an older & unavailable 3.3.3.

On Mac OS X, the homebrew package manager should help. After installing homebrew, run:

$ brew install maven 

The OS X package manager MacPorts can also install Maven 3 via sudo port install maven3.

Double-check Java and Maven prerequisites

Use the command mvn --version to confirm that Maven 3.3 or later is installed. Output should look like:

% mvn --version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
Maven home: /opt/local/share/java/maven3
Java version: 1.8.0_91, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"

Some OS X users have had problems where the version of Maven installed by MacPorts uses a different Java version than expected. Java version 1.8 or later is required. If Java 1.7 or earlier is reported, then refer to this StackOverflow Maven JDK mismatch question.

Building Corfu

Once you've installed the prerequisites, you can build Corfu.

$ mvn clean install

The binaries which will be referenced in the following sections will be located in the bin directory.

Running Corfu for the first time

The Corfu infrastructure is provided by the monolithic binary corfu_server. For testing purposes, you will want to run the server in in-memory, single-server mode. To do this, run:

$ ./CorfuDB/bin/corfu_server -ms 9000

This starts an in-memory single node Corfu infrastructure on port 9000. To point clients at this infrastructure, point them at localhost:9000.

How do I make sure it works?

To test your Corfu infrastructure, you can use the Corfu utilities. One of the first things you might want to do is check is the layout, which described the configuration of servers in the Corfu infrastructure. To run this, try:

$ ./CorfuDB/bin/corfu_layouts -c localhost:9000 query

You should get output similar to this:

  "layoutServers": [
  "sequencers": [
  "segments": [
      "replicationMode": "CHAIN_REPLICATION",
      "start": 0,
      "end": -1,
      "stripes": [
          "logServers": [
  "epoch": 0

This means that the infrastructure is currently configured with a single layout server, a single sequencer, and a single replica which is replicated using chain replication.

Now we can try writing to the instance. The stream utility can be used to write to the instance:

$ echo "hello world" | ./CorfuDB/bin/corfu_stream append -c localhost:9000 -i test

This utility takes input from stdin and writes it into the log. This command invocation writes a entry named "hello world" to a stream called "test". Streams are a kind of virtualized log in Corfu - think of them as append-only files.

Next, we can try reading back that stream. This can be done by running:

$ ./CorfuDB/bin/corfu_stream read -c localhost:9000 -i test

The utility should print back "hello world".

Cool, it works! But how do I make it distributed?

Now that you have a working Corfu deployment, you'll probably want to make it distributed.

Let's start by adding a layout server. To do that, start a non-provisioned Corfu server instance in addition to the previous one. We'll start it on port 9001.

$ ./CorfuDB/bin/corfu_server -m -M localhost:9000 9001

Now let's add that layout server to the previous deployment:

$ ./CorfuDB/bin/corfu_layouts -c localhost:9000 edit

This should bring up your editor. If you modify the layoutServers line to read:

  "layoutServers": [
    "localhost:9000", "localhost:9001"

This will install that server as a new layout server.

If you check the current layout using the query command:

$ ./CorfuDB/bin/corfu_layouts query -c localhost:9000,localhost:9001

You will see that you now have two servers in the layout.

How about adding an additional replica so we can tolerate a single log server failure? We can use the same corfu_server on port 9001. Recall that corfu_server is a monolithic binary containing all servers. Since we have not yet pointed to the log server on 9001, that server has started but is not in use.

To add a replica, we edit the layout again:

$ ./CorfuDB/bin/corfu_layouts edit -c localhost:9000,localhost:9001

You'll want to add localhost:9001 as a new logunit to the existing segment:

      "logServers": [

This adds the log unit at localhost:9001 to the only segment in the system. to learn more about segments, see the Corfu wiki.

To scale Corfu, we add additional ``stripes''. To add an additional stripe, first start a new corfu_server on port 9002:

./CorfuDB/bin/corfu_server -m -M localhost:9000 9002

Add this layout server to the previous deployment by editing the layout:

$ ./CorfuDB/bin/corfu_layouts edit -c localhost:9000,localhost:9001

The layoutServers line should read:

  "layoutServers": [
    "localhost:9000", "localhost:9001", "localhost:9002"

This time we add localhost:9002 as a new stripe.

      "stripes": [
          "logServers": [
          "logServers": [

This adds the logunit at localhost:9002 as an additional stripe in the system. That is, writes to even addresses will now go to localhost:9000 and localhost:9001, while writes to odd addresses will go to localhost:9002.

Now I want to write a program that uses Corfu!

To write your first program that uses Corfu, you will want to add Corfu as a dependency. For Maven-based projects, you can add:


to your pom.xml file.

You will also want to add the Corfu Maven repository, unless you ran mvn install from source to install the jar files locally:


Once you have Corfu added as a dependency, you can start writing Corfu code. Let's start with a map:

    CorfuRuntime rt = new CorfuRuntime("localhost:9000")

    Map<String,Integer> map = rt.getObjectsView()

    Integer previous = map.get("a");
    if (previous == null) {
        System.out.println("This is the first time we were run!");
        map.put("a", 1);
    else {
        map.put("a", ++previous);
        System.out.println("This is the " + previous + " time we were run!");

You can run this code multiple times from many clients, and each client should display a unique "run".