Marcus Feld

Hi, I’m Marcus, the Infrastructure Editor here. If a question starts with “what is actually happening on the server?”, it has usually landed on my desk. I also cover performance and security, because in my experience those three are really one conversation wearing different hats.

I grew up with this

I’ve been around web hosting since I was a teenager running a game server off a humming box in my bedroom, learning Linux by breaking it and finding out what it feels like to watch your own site fall over on a Friday night. That curiosity turned into a first job on the support desk of a small regional host, answering tickets by day and swapping failed drives in the racks by night. It taught me the thing no brochure mentions, which is how shared hosting really behaves once it has been oversold.

From there I spent a decade as a data centre systems engineer, running fleets of virtual servers and the occasional stubborn physical machine, carrying the on-call pager, and being the person who gets the 2 a.m. alert when something important stops responding. Years of that leave you with a healthy suspicion of marketing pages. So when I look at a plan now, I skip the adjectives and ask what is physically running the site and who else is sharing it.

Translating the labels

Most hosting confusion comes from words. “Cloud”, “VPS”, “managed” and “unlimited” describe a sales package, not a machine. I translate every plan into plain questions. How much processor and memory is guaranteed, and how much is only borrowed when the machine is quiet? What storage sits underneath? How far is it from your visitors? And what happens when a neighbour on the same server misbehaves? That last one explains more mystery slowdowns than anything else.

The things I go on about

If I could keep one performance number it would be time to first byte, the wait before any data arrives. It points straight at an overloaded server, slow storage, a heavy query or a missing cache, long before any front end tweak matters.

I care about security the way a mechanic cares about brakes, quietly and before there is a problem. Most of what protects a site is unglamorous, a certificate that renews itself, software kept updated, strong unique passwords with two factor sign in, and backups kept somewhere other than the server itself. A backup you have never restored is a hope, not a plan.

Matching the tool to the job

My advice is rarely “buy the biggest thing”. A small site wants a decent shared plan with caching. A busy store or a bursty site is where a VPS or cloud instance earns its price. Dedicated hardware suits steady, heavy loads and people with the skills to run it. For most, that is expensive overkill, and I will happily say so.