<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Darshan Modi</title>
    <description>The latest articles on DEV Community by Darshan Modi (@darshanmodi07).</description>
    <link>https://dev.to/darshanmodi07</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4156518%2F705b4dc9-a54d-4772-9015-aafcba3c74e0.jpg</url>
      <title>DEV Community: Darshan Modi</title>
      <link>https://dev.to/darshanmodi07</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/darshanmodi07"/>
    <language>en</language>
    <item>
      <title>What Actually Happens When an API Request Hits Your Backend?</title>
      <dc:creator>Darshan Modi</dc:creator>
      <pubDate>Fri, 02 Oct 2026 06:37:36 +0000</pubDate>
      <link>https://dev.to/darshanmodi07/what-actually-happens-when-an-api-request-hits-your-backend-3n5o</link>
      <guid>https://dev.to/darshanmodi07/what-actually-happens-when-an-api-request-hits-your-backend-3n5o</guid>
      <description>&lt;p&gt;Ever wondered what happens after you click &lt;strong&gt;"Send"&lt;/strong&gt; on an API request?&lt;/p&gt;

&lt;p&gt;A typical backend request goes through these stages:&lt;/p&gt;

&lt;p&gt;Client&lt;br&gt;
↓&lt;br&gt;
HTTP Request&lt;br&gt;
↓&lt;br&gt;
Middleware&lt;br&gt;
↓&lt;br&gt;
Parsing&lt;br&gt;
↓&lt;br&gt;
Validation&lt;br&gt;
↓&lt;br&gt;
Authentication&lt;br&gt;
↓&lt;br&gt;
Authorization&lt;br&gt;
↓&lt;br&gt;
Business Logic&lt;br&gt;
↓&lt;br&gt;
Database&lt;br&gt;
↓&lt;br&gt;
HTTP Response&lt;br&gt;
↓&lt;br&gt;
Client&lt;/p&gt;

&lt;p&gt;Each stage has a different responsibility.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Parsing&lt;/strong&gt; → Understand the incoming data&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validation&lt;/strong&gt; → Check whether the data is valid&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authentication&lt;/strong&gt; → Who are you?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authorization&lt;/strong&gt; → Are you allowed to do this?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business Logic&lt;/strong&gt; → What should the application do?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database&lt;/strong&gt; → Store or retrieve data&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Response&lt;/strong&gt; → Send the result back to the client&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Understanding this flow helped me stop thinking of an API as just a route and start seeing it as a complete request lifecycle.&lt;/p&gt;

&lt;p&gt;That's the foundation I'm building as I learn backend engineering. 🚀&lt;/p&gt;

&lt;h1&gt;
  
  
  backend #javascript #nodejs #webdev
&lt;/h1&gt;

</description>
      <category>api</category>
      <category>architecture</category>
      <category>backend</category>
      <category>softwareengineering</category>
    </item>
  </channel>
</rss>
