Phil Eaton Portfolio
Personal site of a database-internals engineer (ex-Oracle, ex-EnterpriseDB, former TigerBeetle co-founder) who is now bootstrapping The Consensus, a research-and-analysis publication for experienced programmers. He writes from-scratch implementations of Raft, MVCC and small SQL databases, and runs a Software Internals Book Club that the site puts at 3,600+ members.
Location
Location: classified. Send a pigeon.
Skills
Notable
- Runs the Software Internals Book Club (3,600+ members, per the site)
- Runs /r/databasedevelopment (10k+ members) and the Software Internals Discord (9k+ members), per the site
- Writing cited in the Manning book Writing for Developers
- goraft, a basic Raft implementation in Go: 240 GitHub stars
What makes it work
A breakdown of the choices that make this portfolio stand out.
Build-it-yourself posts instead of explainer posts
Rather than summarizing how Raft or a write-ahead log works, his posts walk through building a minimal working version from scratch, with the code alongside the explanation — a format that proves understanding rather than just describing it.
Community infrastructure attached to the writing
A companion subreddit, Discord and book club turn a solo blog into a hub other systems programmers gravitate to, which compounds the credibility of the writing itself.
A narrow, consistent topic focus
The blog's most-used tags are databases (55 posts) and postgres (34), and the highlighted posts cluster around MVCC, consensus, disk IO and garbage collectors. That focus makes the site legible as "the databases person" rather than a general tech blog, which is exactly the reputation that leads to database-engineering job offers.
What Backend Developers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Pick one narrow technical area and let most of your posts orbit it — a focused site builds a reputation faster than a broad one.
Show a minimal working implementation of the concept you're explaining, not just a description of how it works.
If your writing attracts a community, give it a place to gather (a subreddit, Discord, or book club) instead of leaving it scattered across comment sections.
Projects
Phil Eaton's projects are pedagogical on purpose: a Raft in Go, another in Rust, and an MVCC engine small enough to read in one sitting, each written up alongside its code.
Implementing Raft in Go
A basic implementation of the Raft consensus protocol in Go, published with a long-form post that walks through building it step by step.
Shows he understands consensus well enough to build it, not just summarize it.
The code and the explanation ship together
Followed by a second minimal Raft in Rust
Implementing MVCC and SQL isolation levels
A small, teaching-oriented implementation of multi-version concurrency control and the major SQL transaction isolation levels, published with a post that explains each level through the code.
Isolation levels are where database bugs hide, and this shows he can build each level and explain it.
Covers the major SQL isolation levels in one codebase
Written as a teaching implementation
The Consensus
A bootstrapped publication of research and analysis on software infrastructure for experienced programmers. It publishes deep dives (Cassandra 6 transactions, SQLite's WAL-reset bug, ThreadSanitizer limits) plus infrastructure jobs, a funding feed and a weekly newsletter.
Turns a database-internals writing habit into a product with a jobs feed and a funding feed.
Reproduces real bugs, e.g. the SQLite WAL-reset race, with a 100-line C workload
Hosts guest authors alongside his own deep dives
More Backend Developer portfolios
Ready to build your portfolio?
Follow the Backend Developer roadmap — skills, projects, and timeline to get hired.