Bare-metal vs vps vs serverless

On a daily basis, I see many people persevering in the default same decision: vintage bare-metal or a VPS is “the fastest answer” to all our human problems even on what so called “cloud” entire teams continuosly persevere in same old direction and I get it because we are human. We stick with what feels familiar, what seems easy, and what already works. If it works, why change it… right? Well, not for me! I never follow the masses

Why I opted out of a traditional model

It’s simple as I want to care about content, not the ongoing management of servers and applications. But it’s not just about avoiding ops work it’s about choosing a model that matches the real goal.

For a personal website, I don’t want to spend my time thinking about:

• patching and upgrading OS
• hardening SSH and managing firewall rules
• babysitting NGINX configs and TLS renewals
• monitoring disk space, backups, and uptime
• keeping dependencies compatible after upgrades
• dealing with “it worked yesterday” WTFFFFFFFFFF surprises for things I don’t own or manage

I’ve done that for years. I know how to do it. I even enjoyed and continue with it when it’s the core of the project but for this website, it’s not the core.

What I wanted was simplicity, and by simplicity I mean:

• fewer moving parts
• fewer things that can break
• fewer decisions to maintain over time
• a workflow that lets me publish quickly and move on

I spent over a decade on Cloudflare and with trust I choose the Cloudflare Pages to support my astro website allowing me to on writing, shipping, and iterating while the platform handles the boring parts in the background.

Because the best infrastructure is the one you don’t have to think about.