Feat: Improving backend file structure

[kunal697]

What would you like to see?

Proposed Backend Folder Structure Improvement

Current Structure:

server/src/
├── routes/        # API routes
├── config/        # Server configuration
├── utils/         # Server utilities
└── validators/    # Request validation

Proposed Structure:

server/
└── src/
    ├── handlers/
    │   ├── <moduleName>/
    │   │   ├── <moduleName>Controller.js   # Handles route logic, calls services
    │   │   └── <moduleName>Services.js     # Business logic and functions
    │
    ├── routes/
    │   ├── <moduleName>/
    │   │   └── route.js                    # Maps routes to controllers

---

Example – Auth Module

server/
└── src/
    ├── handlers/
    │   └── auth/
    │       ├── authController.js   # Connects routes with service functions
    │       └── authServices.js     # Contains authentication logic
    │
    ├── routes/
    │   └── auth/
    │       └── route.js            # Defines auth routes and maps them to controller

Why is this feature useful?

Benefits:

• Clear separation of concerns (Routes → Controller → Service).
• Easier to scale and maintain.
• Consistent module-based structure.

Have you considered any alternatives?

No response

Additional context or visuals

No response

[bossadizenith]

Okay i think it's a solid proposition. we'll be migrating to this next week end. given the current structure already works for the launch.

[kunal697]

You can assign this to me , and ping me once we can start working on this after a stable repo

[bossadizenith]

okay however make sure every changes done should be tested before pushing.