<?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: Karthick </title>
    <description>The latest articles on DEV Community by Karthick  (@karthickthangavel).</description>
    <link>https://dev.to/karthickthangavel</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%2F1432796%2F6748755f-524a-494e-996c-76e5cb049524.jpeg</url>
      <title>DEV Community: Karthick </title>
      <link>https://dev.to/karthickthangavel</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/karthickthangavel"/>
    <language>en</language>
    <item>
      <title>🏗 Designing Public &amp; Admin Routes Properly in Express (Node.js + TypeScript)</title>
      <dc:creator>Karthick </dc:creator>
      <pubDate>Thu, 26 Feb 2026 04:56:11 +0000</pubDate>
      <link>https://dev.to/karthickthangavel/designing-public-admin-routes-properly-in-express-nodejs-typescript-926</link>
      <guid>https://dev.to/karthickthangavel/designing-public-admin-routes-properly-in-express-nodejs-typescript-926</guid>
      <description>&lt;p&gt;When building a scalable backend API, one common question is:&lt;/p&gt;

&lt;p&gt;Should we separate admin routes like /api/admin/categories&lt;br&gt;
Or protect routes using middleware?&lt;/p&gt;

&lt;p&gt;In this article, I’ll show you the clean and scalable way to structure public and admin routes.&lt;/p&gt;

&lt;p&gt;🚀 The Use Case&lt;/p&gt;

&lt;p&gt;We are building a Blog System with categories.&lt;/p&gt;

&lt;p&gt;We need:&lt;/p&gt;

&lt;p&gt;Public users → View all categories&lt;/p&gt;

&lt;p&gt;Admin users → Create categories&lt;/p&gt;

&lt;p&gt;&lt;code&gt;❌ Bad Practice (URL-Based Role Separation)&lt;br&gt;
POST /api/admin/categories&lt;br&gt;
GET  /api/categories&lt;br&gt;
&lt;/code&gt;&lt;br&gt;
Why this is not ideal?&lt;/p&gt;

&lt;p&gt;URL becomes tightly coupled with roles&lt;/p&gt;

&lt;p&gt;Harder to scale&lt;/p&gt;

&lt;p&gt;Not RESTful&lt;/p&gt;

&lt;p&gt;Role logic leaks into routing&lt;/p&gt;

&lt;p&gt;✅ Recommended Approach (Middleware-Based Authorization)&lt;/p&gt;

&lt;p&gt;Keep URLs clean and RESTful.&lt;/p&gt;

&lt;p&gt;GET    /api/categories        → Public&lt;br&gt;
POST   /api/categories        → Admin only&lt;/p&gt;

&lt;p&gt;Access control should be handled by middleware, not the URL.&lt;/p&gt;

&lt;p&gt;📂 Project Structure (Feature-Based Architecture)&lt;br&gt;
src/&lt;br&gt;
 ├── modules/&lt;br&gt;
 │    ├── categories/&lt;br&gt;
 │    │    ├── categories.controller.ts&lt;br&gt;
 │    │    ├── categories.service.ts&lt;br&gt;
 │    │    ├── categories.routes.ts&lt;br&gt;
 │    │    ├── categories.model.ts&lt;br&gt;
 │&lt;br&gt;
 ├── middleware/&lt;br&gt;
 │    ├── auth.middleware.ts&lt;br&gt;
 │    ├── admin.middleware.ts&lt;/p&gt;

&lt;p&gt;This structure keeps everything modular and scalable.&lt;/p&gt;

&lt;p&gt;🛣 categories.routes.ts&lt;br&gt;
import { Router } from "express";&lt;br&gt;
import { CategoriesController } from "./categories.controller";&lt;br&gt;
import { authMiddleware } from "../../middleware/auth.middleware";&lt;br&gt;
import { adminMiddleware } from "../../middleware/admin.middleware";&lt;/p&gt;

&lt;p&gt;const router = Router();&lt;/p&gt;

&lt;p&gt;/* ---------- PUBLIC ROUTE ---------- */&lt;br&gt;
router.get("/", CategoriesController.getAll);&lt;/p&gt;

&lt;p&gt;/* ---------- ADMIN ROUTE ---------- */&lt;br&gt;
router.post(&lt;br&gt;
  "/",&lt;br&gt;
  authMiddleware,&lt;br&gt;
  adminMiddleware,&lt;br&gt;
  CategoriesController.create&lt;br&gt;
);&lt;/p&gt;

&lt;p&gt;export default router;&lt;br&gt;
🔐 Why Middleware-Based Authorization is Better&lt;/p&gt;

&lt;p&gt;✅ Clean RESTful design&lt;br&gt;
✅ Scalable for future roles (editor, moderator, etc.)&lt;br&gt;
✅ Separation of concerns&lt;br&gt;
✅ Professional backend structure&lt;/p&gt;

&lt;p&gt;🏆 Final API Design&lt;br&gt;
Method  Endpoint    Access&lt;br&gt;
GET /api/categories Public&lt;br&gt;
POST    /api/categories Admin&lt;br&gt;
PUT /api/categories/:id Admin&lt;br&gt;
DELETE  /api/categories/:id Admin&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
