The Buka Series [Part 1]

When you're asked in a technical interview to explain what HTTP is...

After you mention it's a protocol (HyperText Transfer Protocol) used to transfer data over the web...

Please, don’t stop there. That’s just the abbreviation.

What you really want to explain is how HTTP works and why it matters in real-world applications.

Now, use this simple analogy to understand that dude once and for all:

Think of HTTP like sending someone to get amala from your favorite buka.

You (the client) are hungry.
The buka (a local food spot or street restaurant) which is regarded as the server has what you want.
But you’re not going yourself, you’re sending a trusted guy (HTTP) to go there, collect it, and bring it back.

Here’s how it plays out:

• You tell him what you want: “GET me amala, abula (a Nigerian soup) and ogunfe (goat meat) 🤤.”

• Or you say: “POST this new meal idea — mixed rice and beans with palm oil stew — into their suggestion box.”

• You could even say: “PUT this correction in my usual order.” or “DELETE my order entirely.”

When he gets back, he gives you a report:

• 200 — All went well. Here’s your food.

• 404 — Buka no get amala today.

• 500 — Kitchen catch fire. Everything scatter.

He also gives you some notes (headers):

• “The buka says next time come early o.”

• “They served it hot 🔥, and they added ponmo (cow skin) for free.”

And the actual food itself? That’s the body of the response. That’s what you really needed.

But here’s the funny thing, the guy forgets you after every trip 😭.
Unless you hand him a token or cookie like “This is from me, Usman. They know me there.”

That’s HTTP: stateless, structured, fast — and when upgraded (HTTP/2, HTTP/3), he now moves faster, delivers multiple orders at once, and dodges Lagos traffic like a pro 😁.

So the next time someone asks you, “What is HTTP?”
Smile.
And tell them: “He’s my trusted delivery guy, carrying my web messages back and forth. Clean, clear, and fast.”

At least I can't be in the interview room with you...

But if this post helps you walk in more confidently, that’s good enough for me.

Check out the next part for HTTPS
See you in the Next!