Work · Noa Kessling

NKESSLING@TERMINALSCREEN WORKOpen to work from Nov 2026RTM 17:28:39 · UTC 15:28

WORK ~/work

Storage engines, build tools and queues. Every project shows the problem, the file that fixed it and the numbers after.

PROJECTS: 8
STARS: 11.7K
LANGUAGES: Rust · Go · TS · Zig
SINCE: 2017

SCRN WORK · SCREENER8 OF 8 SHOWN

All projects, screened.

Filter by language, sort any column, and hover a row for the preview.

ROLEKEY RESULT

TIDEA write-ahead log that survives the power cordtidewaterAuthor · maintainerRust2024–264,8121.92 GB/s append, one core KILNA build cache that made CI six times fasterkilnAuthorGo2023–262,2076.1x faster CI, median LOOMA Postgres job queue that stays fair under loadloom-queueAuthor · 3 contributorsTypeScript2024–251,39012k/s jobs on one node WRENRelease notes that write themselves from commitswrenAuthorTypeScript2025–261,04511 min saved per release PRSMRead traces in the terminal and diff two runsprism-traceAuthorRust2025961O(n log n) trace diff, was O(n²)FERNA small config language with typesfernAuthorZig2025–266120.4 ms compile a 2k-line config SLABAn arena allocator with checked handlesslab-arenaAuthorRust20233883.1x faster than Box in the hot loop DOCKA local cluster with real DNS and TLS in one commanddocksideAuthorGo202427438 s cold start to green

F3 REPOS · 4 PROJECTS
PROJECT 01 / 04 · AUTHOR · MAINTAINER
A write-ahead log that survives the power cord.Embedded databases lose data when they fsync too little and crawl when they fsync too often. tidewater groups writes, rotates segments safely and replays in one pass after a crash.
1.92 GB/sappend, one core
2.1 msp99 group commit
0lost writes in 40k crash tests
STACK Rust · io_uring · property tests
CASE STUDY <GO>README
Open a project the way you would open the repo.
nkessling / tidewater⑂ mainRust★ 4,812⑂ 211last commit 2h ago
FILES
README.mdrendered
# tidewaterCrash-safe write-ahead log for embedded databases.
buildpassingcrate2.1.0msrv1.76licenseMIT
## WhyGroup commit batches concurrent writers into one fsync. After a segment rotates, the directory is fsynced too, so a crash can never leave a segment the log cannot find.
## Install$ cargo add tidewater## Numbersworkloadtidewaterfsync each write
append 4 KiB1.92 GB/s0.21 GB/s
p99 commit2.1 ms9.8 ms
recovery 8 GB3.4 s11.0 s
Runs under three production databases and one payments ledger.
COMMITS · main8 shown
fix(wal): fsync the directory after a segment rotates
a41f9c2 · 2h ago
Merge #412: group commit for concurrent writers
9e03b71 · 1d ago
group: wake all waiters on one fsync
c7d2a18 · 1d ago · feature branch
group: batch writers behind a ticket lock
51b6e40 · 2d ago · feature branch
bench: 1.92 GB/s sequential append on M3
0f9a3d5 · 3d ago
test: 40k simulated power cuts, 0 lost writes
e2c84b9 · 4d ago
release v2.1.0v2.1.0
7b19f06 · 6d ago
refactor: split recovery into scan and replay
3ad50ce · 8d ago
ACTIVITY · 26 WEEKS · TIDE
README · scroll to continue8 files · 8 recent commits · crate 2.1.0

workload	tidewater	fsync each write
append 4 KiB	1.92 GB/s	0.21 GB/s
p99 commit	2.1 ms	9.8 ms
recovery 8 GB	3.4 s	11.0 s

BENCH BEFORE / AFTER01 / 04

Before and after, measured.

Each project has one number that mattered. Scroll to draw the after line over the before line.

TIDEAppend throughput by record size9.1x
KILNMedian CI time, 30 days6.1x
LOOMQuiet tenant p95 pickup during a burst1,079x
PRSMDiff time by trace size1,166x

TIDE · APPEND THROUGHPUT BY RECORD SIZE

9.1xmore throughput

BEFORE 0.26 GB/sAFTER 1.92 GB/s

record size, 256 B → 64 KiBfsync each write vs group commit, M3, one core

RATE CLIENTS · ANALYST NOTES6 NOTES

What clients wrote afterwards.

Filed like analyst notes: the rating, the result it was based on, and who wrote it.

CONSENSUS6 OF 6 · HIRE AGAIN

0 HOLD · 0 PASS

RATING · HIRE AGAIN0 lost writes since

“Noa found the durability bug we had been blaming on hardware for a year, fixed it, and left us a crash test so it stays fixed.”

Priya RamanCTO · Vantle Ledger

RATING · HIRE AGAINCI 18 m → 3 m

“Our CI went from a coffee break to a sip. The sizing guide alone saved us a quarter of platform work.”

Tomasz WieczorekHead of Platform · Harbourmeal

RATING · HIRE AGAINHandover in 2 days

“Clear writing, clear pull requests, and no surprises. The handover doc read like a good README.”

Amara OkaforEngineering Manager · Norrvik Pay

RATING · HIRE AGAINp95 41 s → 38 ms

“The fair queue change was eight lines and it ended a year of support tickets about slow emails.”

Jonas BrekkeStaff Engineer · Postquill

RATING · HIRE AGAIN−48% code shipped

“Noa asks the question that makes the design smaller. We shipped half the code we planned and it was faster.”

Lucía FerreyraVP Engineering · Tallyroom

RATING · HIRE AGAIN11 → 1 pages/week

“Pages went from eleven a week to one. The team finally took real holidays.”

Daniel OseiSRE Lead · Quaymark Health

Eight projects, each one a repo you can open.

All projects, screened.

# tidewater

## Why

## Install

## Numbers

Before and after, measured.

What clients wrote afterwards.