<?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: Raghav Thaman</title>
    <description>The latest articles on DEV Community by Raghav Thaman (@raghav_thaman).</description>
    <link>https://dev.to/raghav_thaman</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3884371%2Ff4d29283-2533-441d-af9d-5517b15788c2.png</url>
      <title>DEV Community: Raghav Thaman</title>
      <link>https://dev.to/raghav_thaman</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/raghav_thaman"/>
    <language>en</language>
    <item>
      <title>Understanding Middleware Pipeline in ASP.NET Core (Simple Explanation)</title>
      <dc:creator>Raghav Thaman</dc:creator>
      <pubDate>Fri, 17 Apr 2026 11:41:42 +0000</pubDate>
      <link>https://dev.to/raghav_thaman/understanding-middleware-pipeline-in-aspnet-core-simple-explanation-420h</link>
      <guid>https://dev.to/raghav_thaman/understanding-middleware-pipeline-in-aspnet-core-simple-explanation-420h</guid>
      <description>&lt;p&gt;While working with ASP.NET Core, one important concept I learned is the middleware pipeline.&lt;/p&gt;

&lt;p&gt;Middleware is a series of components that process every HTTP request and response in an application.&lt;/p&gt;

&lt;p&gt;Each request passes through multiple middleware components before reaching the controller, and the response goes back through the same pipeline.&lt;/p&gt;

&lt;p&gt;Common middleware examples include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Authentication middleware (checks user identity)&lt;/li&gt;
&lt;li&gt;Logging middleware (records request details)&lt;/li&gt;
&lt;li&gt;Exception handling middleware (handles errors)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The order of middleware is very important. For example, authentication must run before accessing protected endpoints.&lt;/p&gt;

&lt;p&gt;Understanding middleware helps in:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Controlling request flow&lt;/li&gt;
&lt;li&gt;Improving security&lt;/li&gt;
&lt;li&gt;Debugging issues effectively&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This concept is fundamental for building scalable and secure backend applications.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>beginners</category>
      <category>dotnet</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Building a Clean Backend Architecture in ASP.NET Core (Beginner Guide)</title>
      <dc:creator>Raghav Thaman</dc:creator>
      <pubDate>Fri, 17 Apr 2026 11:40:04 +0000</pubDate>
      <link>https://dev.to/raghav_thaman/building-a-clean-backend-architecture-in-aspnet-core-beginner-guide-1802</link>
      <guid>https://dev.to/raghav_thaman/building-a-clean-backend-architecture-in-aspnet-core-beginner-guide-1802</guid>
      <description>&lt;p&gt;While learning backend development with ASP.NET Core, I realized that writing code is not enough — structuring it properly is equally important.&lt;/p&gt;

&lt;p&gt;A clean backend architecture usually follows a layered approach:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Controller Layer&lt;br&gt;&lt;br&gt;
Handles incoming HTTP requests and returns responses.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Service Layer&lt;br&gt;&lt;br&gt;
Contains business logic and processes data.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Repository Layer&lt;br&gt;&lt;br&gt;
Interacts with the database and performs CRUD operations.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Database Layer&lt;br&gt;&lt;br&gt;
Stores and manages application data.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This separation of concerns makes the application:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Easier to maintain
&lt;/li&gt;
&lt;li&gt;More scalable
&lt;/li&gt;
&lt;li&gt;Easier to debug
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, instead of writing all logic inside controllers, we should move business logic into services and database logic into repositories.&lt;/p&gt;

&lt;p&gt;This approach is widely used in real-world backend systems and helps developers build clean and professional applications.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>backend</category>
      <category>beginners</category>
      <category>dotnet</category>
    </item>
  </channel>
</rss>
