development · web

The website with no database

A calm sea reflections

The website with no database (and why yours might be better off without one)

Most websites are carrying weight they do not need.

The usual way to build a small business site is to reach for a content management system, almost always WordPress, bolt on a handful of plugins, and let the whole thing run off a database humming away in the background. Every time someone visits a page, the site wakes up, asks the database a series of questions, assembles the page on the spot, and hands it over. It works. Millions of sites run this way perfectly happily. But it is a lot of machinery for what is often, when you stand back and look at it, a few pages of words and pictures that barely change from one month to the next.

My own site is built a different way, and I want to walk through how, because the difference is the sort of thing that quietly matters to anyone running a business online, even if they never see a line of it.

It has no database.

That sounds like a missing feature. It is the opposite. Instead of building each page fresh every time someone asks for it, the site is built once, in advance, into plain files. Finished pages, sitting ready, waiting to be handed straight over. When you visit, there is nothing to assemble and nothing to ask. The page is simply there. The technical name for this is a static site, and the slightly newer trick of feeding it from a friendly editing tool behind the scenes is called going "headless," but the names matter far less than what they buy you.

Three things, mainly.

It is fast. Properly fast, not "fast for a website" fast. Because the pages already exist and are served from machines dotted around the world close to whoever is asking, they arrive almost the instant you click. There is no waiting while a server thinks. Visitors do not consciously notice speed, but they absolutely notice slowness, usually by leaving, and search engines have a long memory for sites that keep people waiting.

It is hard to break. This is the part I find most satisfying. A database-driven site has a lot of moving parts, and every moving part is something that can go wrong, fall out of date, or be picked at by someone with bad intentions. WordPress, by virtue of running a sizeable chunk of the entire internet, is also the most attacked platform on the entire internet. A static site has almost nothing to attack. No database to break into, no login wired to the public pages, no stack of plugins quietly going stale. There is simply far less of it to go wrong.

And it is close to maintenance-free. No security updates to stay on top of, no plugin that updates itself one Tuesday and takes the contact form down with it, no creeping monthly hosting bill for a server that spends most of its life waiting around. You build it, it sits there being fast and reliable, and it mostly leaves you alone. Which, frankly, is what most people actually want from a website. They want it to work and then to stop being a thing they have to think about.

Now, the honest bit, because I would rather you trusted me than oversold you.

This is not the right answer for everything. If you are running a shop with a thousand products changing prices daily, or a membership site, or anything where lots of people need to log in and do things, a database earns its keep and WordPress may well be the sensible call. I still build plenty on WordPress when WordPress is the right tool. The point is not that one is good and the other is bad. The point is that the default has quietly become "use the heavy thing for everything," and for a great many small business sites, a few pages that need to look sharp, load instantly and never fall over, the heavy thing is solving a problem you do not have.

So if your site feels slow, or you have lost an afternoon to a plugin conflict, or you are paying for hosting that seems to do an awful lot of nothing, it is worth knowing there is another way to build. Quieter, faster, and far less likely to ring you at two in the morning.

My site does not have a database. It has never once gone down. And I have genuinely never had to log in to fix it.

That is the pitch, really. The best technology is the kind you forget is there.