The Delicious Case Study: Origin and MVP

That 2003 cyber cafe in India I mentioned is where we begin. The story of Delicious is the perfect case study because it starts with a problem every developer can relate to - and ends with engineering decisions that still shape how the web works today.

The World in 2003: A Different Era

Before we look at any code, we have to remember what the world looked like in 2003. It was a completely different era:

• No AWS: Amazon Web Services didn't exist until 2006.
• No YouTube: That didn't launch until 2005.
• No Chrome: Most of the world was still stuck on Internet Explorer.
• No Cloud Sync: This was the biggest pain point. If you saved a bookmark in your browser, it stayed on that specific machine.

The Problem: The Cyber Cafe Dilemma

Back then, most people didn't have high-speed internet at home. If you needed to do research, you went to a Cyber Cafe.

Here was the frustrating scenario I remember: You'd sit at Machine A, do your research, and save ten bookmarks. The next day, Machine A is taken, so you sit at Machine B. Your bookmarks are gone. They were trapped on Machine A's local hard drive.

Joshua's realization was simple but powerful: Build a website where users can store their bookmarks on a central server, making them accessible from any computer with an internet connection.

Defining the MVP (Minimal Viable Product)

Joshua didn't start by building a massive enterprise system. He started with an MVP - the smallest set of features that solves a real problem.

For Delicious, the MVP only needed three things:

1. Register and Login: So the system knows who you are.
2. Add a Bookmark: Just save a URL.
3. View Bookmarks: See your list.

I noticed something interesting here: things like Logout, Delete, Tags, or Thumbnails weren't even in the initial plan. The MVP only cares about one thing: proving that people actually want to save bookmarks to the cloud.

Networking 101: Connecting the World

Once the code is written, you need to get it on the internet so a student in another city can access it. This requires three basic layers:

The ISP (Internet Service Provider)

Everything starts with the ISP - companies like Jio, Airtel, or Comcast. They run the physical fiber or copper cables to your home.

The Router

The router takes that physical connection and broadcasts it to your devices via Wi-Fi.

The IP Address

The moment a device connects to the internet, it gets an IP Address. It is a unique identifier, like a postal address. If a user knows your IP address, their laptop can find your server across the global network.

But here is the catch: nobody can be expected to type 142.250.190.46 every time they want to visit a site. In the next part, I will show you how we solve the "Name vs. Address" problem using the most important directory on the planet.

The Essentials

1. A great product starts with an MVP - the smallest possible feature set that proves people want the thing. Delicious launched with just register, add bookmark, and view bookmarks.
2. Every internet-connected device gets an IP Address - the machine-readable identifier that lets your server be found anywhere in the world.
3. The hardest part of scaling is not writing the code - it is dealing with the infrastructure and connectivity layers that sit beneath it.

Further Reading and Watching

• TechWorld with Nana - What is a REST API? - A clear explanation of how clients talk to servers, which is the foundation of every web MVP.
• Mozilla MDN - How the Web Works - The authoritative reference for understanding the browser-server-DNS chain from first principles.