LIVE DEMO

Nebula Cluster: a database that stays up

Watch three servers hold one database between them: send a write to any server, see it acknowledged once most of them have it, stop the leader and watch another take over, cut a leader off in the middle of a write, give your applications one address with the router, add a fourth server and empty an old one with a statement each, and lose a server for good to watch the cluster make its copy again.

Nebula Cluster: a database that stays up: Watch three servers hold one database between them: send a write to any server, see it acknowledged once most of them have it, stop the leader and watch another take over, cut a leader off in the middle of a write, give your applications one address with the router, add a fourth server and empty an old one with a statement each, and lose a server for good to watch the cluster make its copy again.

This interactive demo needs WebGL. Read about it.

Nebula Cluster: a database that stays upOpen the full demo →

What you are looking at

Three servers hold one database, orders, between them. Each holds a full copy. One of them leads at any moment, and has the lime frame. Your application, on the left, is connected to one server over plain Bolt; click a server to connect it to another.

The row of squares under each server is the end of its log. An entry is amber when it has been written and green once most of the servers have it on disk, which is the moment the write is acknowledged.

The change of leader plays at the speed we measured. Everything else is slowed down so you can follow it.

Things to try

The numbers

With three server processes and the default timings, a write sent through another server was accepted 2.6 seconds after we killed the leader's process: between 2,562 and 2,624 ms in six runs out of six. The three ran on one machine, so that figure has no network delay in it.

The code that decides who leads and what is committed is our own, written on the standard library alone. Before any server ran it, a simulator ran it one million times for 10,000 steps each, delaying, reordering, duplicating and dropping messages, cutting links and crashing servers. Those runs committed 367 million entries, elected 7.5 million leaders and checked 154.6 million reads against what they should have seen, with no rule broken.

Measured on Nebula Cluster 3.0.0-alpha.1, 19 November 2026, on an Intel Core i9-13900K with 64 GB of RAM.

The ten minutes a server may be gone before its copies are made again is the default, and a setting.

Learn more