<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Unfolding Client Server Architecture]]></title><description><![CDATA[Unfolding Client Server Architecture]]></description><link>https://unfolding-client-server-architecture.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Mon, 21 Sep 2026 20:05:22 GMT</lastBuildDate><atom:link href="https://unfolding-client-server-architecture.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Unfolding the Client Server Architecture]]></title><description><![CDATA[From Client-Server to Web-Hosting: A begginer’s Guide🌐💻
Have you ever heard of terms like Client-Server, 🤔Let us go on a journey of understanding What is Client, Server, and Client Server Architecture🚀
Client👨‍💻📱
A client is a computer that re...]]></description><link>https://unfolding-client-server-architecture.hashnode.dev/unfolding-the-client-server-architecture</link><guid isPermaLink="true">https://unfolding-client-server-architecture.hashnode.dev/unfolding-the-client-server-architecture</guid><category><![CDATA[ChaiCode]]></category><category><![CDATA[client-server]]></category><dc:creator><![CDATA[Sumit Raskar]]></dc:creator><pubDate>Fri, 17 Jan 2025 09:11:19 GMT</pubDate><content:encoded><![CDATA[<h2 id="heading-from-client-server-to-web-hosting-a-begginers-guide">From Client-Server to Web-Hosting: A begginer’s Guide🌐💻</h2>
<p>Have you ever heard of terms like Client-Server, 🤔Let us go on a journey of understanding What is Client, Server, and Client Server Architecture🚀</p>
<h2 id="heading-client">Client👨‍💻📱</h2>
<p>A client is a computer that requests information from another computer or server. The client can be anything: a Laptop, Smartphone, Tablet, or Desktop. The server doesn't need to be in a remote place away from the client. The server and client can also be in one system and communicate and connect via interprocess communication techniques, such as Internet Sockets and the Internet Protocol Suite. A client can communicate with servers in a Distant location.🌎</p>
<p><img src="https://img.freepik.com/free-photo/elevated-view-laptop-with-blank-white-screen-cellphone-wooden-desk_23-2147924351.jpg?t=st=1737102781~exp=1737106381~hmac=64bbc4b9c8022c715b92ee37bec6022677f1266cafacf7655d369df351e560fd&amp;w=1800" alt class="image--center mx-auto" /></p>
<h3 id="heading-types-of-client">Types of Client</h3>
<ol>
<li><p>Thick Client🖥️</p>
<p> A computer or machine that performs bulks and bulks of data processing operations on its own is called a Thick client. They do not rely on servers. A personal Computer is a common example of a thick client. They are also called Rich clients or fat clients.</p>
</li>
<li><p>Thin Client🌐</p>
<p> A thin client generally processes data provided by an Application Server. Its role is to present the data provided by the server. Web applications like office web apps are examples of thin clients.</p>
</li>
<li><p>Diskless node💾🔗</p>
<p> It is a hybrid of Thick client and thin client. It processes data locally but relies on a server for storing the data.</p>
</li>
</ol>
<h2 id="heading-server">Server🖥️📡</h2>
<p>A server is a computer that provides information to another computer called a client. On a computer network, this process is called Cllient- Server Architecture. Servers provide various services like media streaming, file sharing, etc. A single server can handle multiple clients. Typically servers are database servers, file servers, print servers, etc.</p>
<p><img src="https://imgs.search.brave.com/sh0oCsypm0k0ypUgB3fE81MeEoTLFmfwrVIbI6xbHfw/rs:fit:500:0:0:0/g:ce/aHR0cHM6Ly90NC5m/dGNkbi5uZXQvanBn/LzExLzI3LzY5LzM3/LzM2MF9GXzExMjc2/OTM3NjdfQ2I1VFlp/OUFaS0JZWlBiREtI/NTNWS2oxMlBtRXNu/NzYuanBn" alt class="image--center mx-auto" /></p>
<h2 id="heading-client-server-architecture">Client Server Architecture⚙️📶</h2>
<p>Now let's see how this architecture works. First, you make a request to the server over the Internet. The query goes to the server, which processes it and returns a response to the client. The client's browser then displays the response on the screen. Let's understand this with an example: you ask your friend to pass you a book. Your request for the book is like the client's request, and your friend handing you the book is like the server's response. This is how Client-Server Architecture works.</p>
<p><img src="https://jaro-website.s3.ap-south-1.amazonaws.com/2024/05/client-server-architecture.png" alt class="image--center mx-auto" /></p>
<h1 id="heading-http-request-response-cycle">HTTP Request-Response Cycle🔁</h1>
<p>We saw what is Client-Server Architecture. But how they communicate is now the big question. Let’s have a breakdown of this🛠️</p>
<h2 id="heading-components-of-http-request-response-cycle">Components of HTTP Request-Response Cycle</h2>
<ol>
<li><p><strong>Client</strong>: The entity (like a web browser, mobile app, or REST client) that starts the request.🖥️</p>
</li>
<li><p><strong>Server</strong>: The machine or service that handles the request and sends back a response.📡</p>
</li>
<li><p><strong>HTTP Methods</strong>: Indicate the action to be taken on the resource (such as GET, POST, PUT, DELETE).🛑✍️</p>
</li>
<li><p><strong>URL (Uniform Resource Locator)</strong>: Indicates the resource's location on the server.🌍</p>
</li>
<li><p><strong>Headers</strong>: Metadata included in the request or response, such as content type, authorization, and cookies.📄</p>
</li>
<li><p><strong>Body</strong>: The data sent in the request (for POST, PUT) or response (like HTML content, JSON).📝</p>
</li>
</ol>
<h2 id="heading-steps-of-http-request-response-cycle">Steps of HTTP Request-Response Cycle</h2>
<ol>
<li><p><strong>Client Sends a Request</strong>:</p>
<ul>
<li>The client creates an HTTP request.</li>
</ul>
</li>
<li><p><strong>DNS Resolution</strong>:🌐➡️🔢</p>
<ul>
<li>The browser converts the domain name (e.g., <a target="_blank" href="http://www.example.com"><code>www.example.com</code></a>) into an IP address using the Domain Name System (DNS).</li>
</ul>
</li>
<li><p><strong>TCP/IP Connection</strong>:🔗</p>
<ul>
<li>A TCP connection is set up between the client and server on port 80 (HTTP) or 443 (HTTPS).</li>
</ul>
</li>
<li><p><strong>Server Receives the Request</strong>:📩</p>
<ul>
<li>The server reads the request and processes it based on the method, headers, and URL.</li>
</ul>
</li>
<li><p><strong>Server Generates a Response</strong>:⚡</p>
<ul>
<li>The server carries out the requested action (e.g., querying a database or retrieving a file).</li>
</ul>
</li>
<li><p><strong>Server Sends the Response</strong>:📤</p>
<ul>
<li>The server sends the response back to the client over the established connection.</li>
</ul>
</li>
<li><p><strong>Client Processes the Response</strong>:✅</p>
<ul>
<li>The client receives and processes the response.</li>
</ul>
</li>
</ol>
<p><img src="https://davisgitonga.dev/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbanner.aa762b2d.png&amp;w=3840&amp;q=75" alt class="image--center mx-auto" /></p>
<h2 id="heading-web-servers">Web Servers🌐🖥️</h2>
<p>A web server is both software and hardware that accepts requests through the HTTP or HTTPS protocol. The resources sent from a web server can be files or static content available on the server, or they can be generated at the time of the request by another program.</p>
<h2 id="heading-web-hosting">Web Hosting🏠🌍</h2>
<p>Web hosting is a service that makes your website accessible on the Internet. Imagine you are renting land to build a house; that land is the web hosting. The house is the website, and the street address is the domain name. Web hosting provides allocated space on a server so that anyone on the internet can access your site.</p>
]]></content:encoded></item></channel></rss>