Skip to main content

Why We Need ISPs

 

Why We Need ISPs

Without ISPs, every business would need a unique wire to every single customer in the world. And every customer would need a unique wire to every business. This is a mess, and it's physically impossible.

ISPs solve this. They act as the middleman. You only need one wire to your ISP, and they handle the rest.

How It All Works

  1. Everyone Connects to an ISP: Clients (like us) connect to an ISP. Businesses (like websites and servers) also connect to an ISP. The ISP gives an IP address to each connected router or device. This is its unique address on the internet.

  2. A Request is Made: When a request for a website comes from you, your ISP's router sees the destination IP address of that website.

  3. The Delivery Job:

    • Same ISP: If the website's IP address is on the same ISP's network, the ISP just sends the data directly to the server.

    • Different ISP: If the website's IP address is on another ISP's network, your ISP sends the request to that other ISP. ISPs have connections with each other, often in big rooms called Internet Exchange Points (IXPs), where they exchange data. 🤝

The Big Picture

This system saves us from the massive complexity and hardware cost of direct connections. Businesses only need a single, high-speed connection to their ISP, and the ISP takes care of getting data to and from every customer in the world. The entire thing is a giant, interconnected web of ISPs that work together to deliver data.


Question to search for:
What is ISP Hierarchy or internet hierarchy?

Comments

Post a Comment

Popular posts from this blog

Java Servlets

  According to me its just a translator, who manages the HTTP requests and handle them to the appropriate function of the API. So then, API turns out to be a term or set of those functions which are kept public. Now let us see in little bit of detail what servlets are: For that we need to see few terms: Static Web Pages: Static web pages are the pages, which are already built, and whose content and design always remain the same.  For Example: About us page of some website. Contact info page of some website Dynamic Web Pages: Dynamic pages are not already defined. They are dependent on search queries. For Example: If we search top 5 books, and click on search button, result would be different. If we search top 5 countries and enter search, result would be different.  So, the search result for every search is different. Working: Now if we have to search static page let's say the first page of any website (which is same for every use in every country) then the process is sim...
Post a Comment
Read more

OnClick and {}

1. The onClick Mystery: Is it the same? Yes, the concept is 90% the same. If you know how to handle a click in plain HTML/JavaScript, you already know how to do it in React. The logic flow is identical: Event: A user does something (Click). Listener: The element hears it ( onClick ). Handler: A specific function runs to deal with it. The "React Twist" (The 10% difference): There are two tiny syntax differences you must memorize: CamelCase: In HTML, it is onclick (lowercase). In React, it is onClick (camelCase). Function, not String: HTML (Old): onclick="doSomething()" (A string of code). React (New): onClick={doSomething} (Passing the actual function itself). So yes, your intuition is correct: Whenever you need to handle logic (clicks, hovers, typing), you will stick to this pattern: on[Event]={functionName} . 2. The Curly Braces { } : The Portal This is the most important syntax rule in JSX. Imagine your code file has two "Modes": HTML Mode: W...
Post a Comment
Read more

Servlet Context and Servlet Config

  Problem without init-parameters? Imagine you write a servlet that connects to a database. If you write the database URL, username, and password directly in your Java code, you have a big problem: What if the database password changes? You have to find the code, change it, recompile the .java file into a .class file, and redeploy the entire application. What if you want to use the same servlet in a different project with a different database? You can't. The code is stuck with the old settings. This is where init parameters come in. They let you move this configuration data out of your code and into the deployment descriptor ( web.xml file). How init-parameters help when we use them in web.xml file? They help us in a way that we don't have to find that particular part of code to change it. And also, it saves us the hectic of changing source code and recompiling that again. Anyone with .war file can change the web.xml file  and use it with class file without having the ne...
Post a Comment
Read more