Do I really need a DB?

First things first: I’m not a DBA, and I don’t pretend to be one.

My obsession with latency and performance

This brings me back to the original question I kept circling around while brainstorming my website architecture on one side, a CMS with all its convenience; on the other side, the desire for near-zero complications including sacrifice of the DB.

So I asked myself a simple question: can I run a website without a database? Can I get rid of it completely?

The Markdown route

Since I’ve been working with Git for a while, nothing feels as simple and reliable as Markdown and very little things can truly replace it. I wanted a frictionless way to produce content, with full confidence that typography and layout would stay consistent, while still allowing me to add media when needed.

Astro makes this incredibly easy. I aligned everything around a straightforward idea: a bucket that contains my content written in pure Markdown like the page you’re reading right now.

No database. No admin panel. No migrations. No runtime dependencies.

Just content, versioned in Git, built fast, and published cleanly.

And voilà mission completed.