BLOG

Blog

Engineering notes, benchmarks and guides from the Galactus DB team.

14/11/2026 · published

The frontier database

A database spends most of its life waiting. The morning rush arrives, the month-end report runs, and in between it sits there holding memory in case somebody needs it. For years we rented that waiting by the gigabyte: memory reserved at start-up, on servers sized for a peak that came on the first of the month.

14/11/2026 · Release

Nearing the theoretical limit: Galactus DB 2.4.3

There is a speed no database can beat: the speed of the work itself, with nothing wasted on the way. For a database that keeps its graph on disk, that speed is easy to find, because we ship it too: the same graph held entirely in memory. In Galactus DB 2.4.3 the two have met. A graph read from pages on disk scans 100,000 people in 8.3 ms where it took 26.2, exactly as long as the engine that keeps everything in memory.

04/11/2026 · Release

Galactus DB 2.2.0: the whole map of Great Britain in a 4 GB container

We loaded every road, building, wood, river and place name in Great Britain into Galactus DB 2.2.0, running in a container capped at 4 GB of memory. That is 16.1 million shapes from Ordnance Survey's VectorMap District, 12 GB of shapefiles. The load took six minutes and never used more than 1.7 GB. A map viewer now draws it straight from the spatial indexes, from a single street to the whole country, at 2 ms per tile.

01/11/2026 · published

Run the graph database benchmark yourself

We have published the benchmark we use to compare Galactus DB with Neo4j and Memgraph. It is one Python script and one Compose file, Apache-2.0, at github.com/galactusdb/galactus-db-benchmark. Clone it, run one command, and it measures all three engines on your machine and writes the results as CSV and a single page of charts. Every number in this post came from that code, and you can check every one of them.

25/10/2026 · Release

Tables on your nodes: SQL inside Galactus DB 2.1

Galactus DB 2.1 lets a node hold tables. A customer keeps its orders, a sensor its readings, an account its ledger, as typed rows with a primary key, indexes and constraints, right on the node they belong to. You read and change them with SQL, in the same statement as your Cypher, in the same transaction. An order stored this way takes 63 bytes on disk instead of 85.

24/10/2026 · Release

Project Orion: Galactus DB 2.0

Galactus DB 2.0 is the biggest change we have made to how your graph is stored. We call it Orion. A database with two million nodes and four million relationships now opens in 0.2 seconds instead of 17, answers reads nearly three times as fast, and does it in a fifth of the memory. Your drivers, your Cypher and your node ids stay exactly as they are.

18/10/2026 · Release

Making time: Galactus DB 1.7.1

Most organisations have a scheduling problem somewhere. Care visits have to fit around staff hours and the drive between clients. An operation needs a surgeon, an anaesthetist and a theatre at the same time. Exams need rooms with enough seats, and a paint line loses an hour every time it changes colour. The answer usually lives in a spreadsheet, or in a separate optimiser that the data has to be exported to.

14/10/2026 · Release

Meanwhile, back at the database: Galactus DB 1.6.2 to 1.6.5

The last time we wrote, in 1.6.1, readers stopped waiting for writers, and we signed off with "nobody waits for anybody, including you". We meant it. Four days and four releases later, here's everything that happened while nobody was waiting.

10/10/2026 · Release

Nobody waits: Galactus DB 1.6.1

Yesterday, in 1.6.0, we stopped readers from holding up writers. Today we returned the favour.

09/10/2026 · Release

Lightning strikes thrice: Galactus DB 1.6.0

They say lightning never strikes the same place twice. This week we took a third off memory, then did it again. We have stopped listening to what they say.

09/10/2026 · Release

We did it again: Galactus DB 1.5.5

Last week we packed Galactus DB a smaller suitcase and celebrated a third less memory. Then we did what everyone does after a holiday: we turned the suitcase upside down to check the pockets.

08/10/2026 · Release

Same graph, smaller suitcase: Galactus DB 1.5.0

Every database has a little admin overhead. A name tag here, a lanyard there, a folder to keep the paperwork in. Ours had been quietly charging every property on every node a 150-byte admin fee before it would even look at the value. A property holding the number 42 was carrying around more filing than a mortgage application.

03/10/2026 · Release

Your graph can now tap you on the shoulder

For most of its life a database is a very good listener and a terrible conversationalist. It remembers everything you tell it, but it never calls back when something changes. If you wanted to know, you asked again. And again. And again, every few seconds, in a loop somebody wrote on a Friday and nobody has dared to touch since.

24/09/2026 · Release

RBAC: the right keys for the right people

Your reporting dashboard needs to read the graph. Your application needs to update it. Neither needs to spend its afternoon creating administrators.

20/09/2026 · Guide

Parks, ponds and paths: giving your graph a sense of place

A pin on a map tells you where something is. It is less helpful when the question is "Can we deliver there?", "Does this route cross the park?" or "Why have we put the meeting point in a pond?"

17/09/2026 · published

A graph database that packs light

Your application has enough to carry without its database arriving with a removal van. Galactus DB ships as a small, self-contained image, with Explorer in a separate package when you want a visual workbench.

17/09/2026 · published

Saved, but how saved? Choosing a durability mode

You press save. The database says "done". Can you put the kettle on, or is there still something waiting to reach disk?

09/10/2026 · published

Galactus DB and Neo4j: a tale of two graph databases

A graph database has a varied working day: find a person, follow a few connections, load a batch of records, then do it all again while everyone else is asking questions too. How do Galactus DB and Neo4j compare at those jobs? Here are the scores, with a little context to help you read them.