Do I Really Need a Database?

First things first: I’m not a DBA, and I don’t pretend to be one. I just want my pages to load before the user blinks.

My obsession with latency and simplicity

When planning this website, I found myself in a classic design dilemma. On one side, the convenience of a modern CMS (with all its administrative weight); on the other, my desire for near-zero complexity.

Near-zero complexity means minimizing runtime points of failure. And the biggest, most common point of failure in any web application is the database.

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

The markdown route

Since I already live in Git for everything I build, nothing feels as simple, reliable, and version-controlled as plain text.

I wanted a frictionless way to write content, with full confidence that typography, code highlighting, and layout would remain consistent. I also wanted to easily add media without uploading files to a bloated asset library in some database-backed admin console.

Astro makes this layout-driven workflow incredibly natural. I built the site around a straightforward architecture: a static content collection written in pure Markdown (exactly like the page you are reading right now).

1. No database connections.
2. No SQL queries or database pools.
3. No migrations to manage.
4. No admin panel logins.
5. No runtime dependencies.

Just raw text files, versioned in Git, compiled into optimized HTML in milliseconds, and served directly from the CDN edge.

Database deleted. Mission accomplished.