JK
Proyectos
JK
>CARGANDO // CARGANDO
INICIALIZANDO VISTA
Creado y diseñado porJK
JK
>CARGANDO // PROJECT DETAILS
PARSING ARCHITECTURE, DIAGRAMS & API ENDPOINTS
Volver a proyectos
Ver en GitHub
Backend API RESTful con Express.js
Completadotypescriptnodejsexpressmongodbcloudinaryjwtdotenveslint

Backend API RESTful con Express.js

Backend API REST listo para producción con arquitectura modular MVC, pipelines de agregación en MongoDB y autenticación segura.

Problema y solución

Crear una base modular sólida con manejo centralizado de errores, cabeceras de seguridad y pruebas automatizadas fiables.

Características

  • Autenticación JWT con rotación de refresh tokens
  • Middleware de autorización basado en roles
  • Optimización de consultas con pipelines de agregación en MongoDB
  • Validación de esquemas y sanitización de entradas
  • Suite de pruebas de integración con Jest y Supertest

Stack tecnológico

TecnologíaVersiónPropósitoPor qué se eligió
Node.js—JavaScript runtimeNon-blocking I/O, large ecosystem
Express.js4.19.2HTTP frameworkMinimal, flexible, well-documented
TypeScript5.5.4Type safetyCompile-time error catching, IDE support
MongoDB—Document databaseFlexible schema, JSON-native, horizontal scaling
Mongoose8.5.3MongoDB ODMSchema validation, middleware, query building
JWT (jsonwebtoken)9.0.2Authentication tokensStateless auth, industry standard
bcrypt5.1.1Password hashingAdaptive hashing, salt rounds
Cloudinary2.4.0Image hosting/CDNManaged service, CDN, image transformations
Multer1.4.5-lts.1File upload handlingExpress-integrated, simple API

Arquitectura

Frontend Client

React :3000

Express App

app.ts :3000

CORS

express.json

JWT Auth Middleware

Global Error Handler

API Routes

/users, /admin, /restaurant, /menuitems, /orders

Controllers

User, Admin, Restaurant, Menu, Order

Mongoose Models

User, Admin, Restaurant, MenuItems, Order

MongoDB

localhost:27017/RMS

Cloudinary CDN

Local Filesystem

uploads
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Application Layers

  • Express.js middleware pipeline (CORS, JSON parsing, JWT auth)
  • Domain-based modular structure (users, adminUser, restaurant, orders)
  • Controllers with direct Mongoose access (no service layer abstraction)
  • Global error handler middleware with status code mapping

Infrastructure

  • MongoDB via Mongoose 8.5.3 for document storage
  • Cloudinary v2 for menu item image hosting and CDN
  • Multer for multipart file upload handling
  • JWT (jsonwebtoken) for stateless authentication

Estructura del proyecto

src
adminUser
config
middlewares
orders
restaurant
users
app.tsExpress app setup, middleware, route mounting
server.tsApplication entry point, starts DB then server

Endpoints de API

RMS API (puerto 3000)

MétodoRutaPropósito
GET/Health check / welcome
POST/api/users/registerRegister new user
POST/api/users/loginLogin user
POST/api/admin/createAdminCreate admin user
POST/api/admin/adminloginLogin admin
POST/api/restaurant/createRestaurantRegister restaurant owner
POST/api/restaurant/ownerLoginLogin restaurant owner
POST/api/Menuitems/addItemsCreate menu item with image
PUT/api/Menuitems/:itemIdUpdate menu item
GET/api/Menuitems/getAllItemsList all menu items
GET/api/Menuitems/:itemIdGet single menu item
DELETE/api/Menuitems/:itemIdDelete menu item
POST/api/orders/createorderCreate order
POST/api/orders/cancelorder/:orderIdCancel order
GET/api/orders/orderdetails/:orderIdGet order details

Diseño de base de datos

users

4 cols
_idPK
ObjectId
name
String
email
String
password
String

admins

4 cols
_idPK
ObjectId
name
String
email
String
userType
String

restaurants

4 cols
_idPK
ObjectId
restaurantName
String
restaurantEmail
String
restaurantPhoneNo
Number

menuitems

5 cols
_idPK
ObjectId
restaurantId
ObjectId
itemName
String
itemPrice
Number
itemImage
String

orders

7 cols
_idPK
ObjectId
customerId
ObjectId
restaurantId
ObjectId
menuId
ObjectId
orderQuantity
Number
orderStatus
String
orderBill
Number
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

users

ColumnaTipoNotas
_idPKObjectIdAuto-generated
nameStringRequired
emailStringRequired, unique
passwordStringbcrypt hashed
createdAtDateAuto (timestamps: true)
updatedAtDateAuto (timestamps: true)

User accounts. Email is unique.

admins

ColumnaTipoNotas
_idPKObjectIdAuto-generated
nameStringRequired
emailStringRequired, unique
passwordStringbcrypt hashed
userTypeStringenum: ['admin', 'user', 'restOwner']

Admin accounts. Separate collection from users.

restaurants

ColumnaTipoNotas
_idPKObjectIdAuto-generated
restaurantEmailStringRequired
restaurantPwdStringbcrypt hashed
restaurantNameStringRequired
restaurantAddressStringRequired
restaurantPhoneNoNumberRequired, unique

Restaurant owner accounts.

menuitems

ColumnaTipoNotas
_idPKObjectIdAuto-generated
restaurantIdObjectIdNo ref defined — .populate() won't work
itemNameStringHas typo: require instead of required
itemDescriptionStringHas typo: require instead of required
itemPriceNumberHas typo: require instead of required
itemImageStringCloudinary URL

Menu items per restaurant. restaurantId lacks ref property — schema bug.

orders

ColumnaTipoNotas
_idPKObjectIdAuto-generated
customerIdObjectIdref: User
restaurantIdObjectIdref: restaurant
menuIdObjectIdref: MenuItems
orderQuantityNumberNo validation for positive values
orderDateDateDefault: Date.now
orderStatusStringenum: ['in process', 'transit', 'cancelled', 'delivered']
orderBillNumberClient-supplied — security concern

Orders are client-supplied bill amounts — no server-side price calculation.

One-to-Many: Users→Orders, Restaurants→MenuItems, Restaurants→Orders, MenuItems→Orders. All via ObjectId references. No many-to-many relationships. menuitems.restaurantId lacks ref property.

Decisiones de diseño clave

Modular Monolith Architecture

Decisión: Single Express.js application with domain-based folder structure

Motivo: Appropriate for project scale (~15 endpoints, single deployment)

Beneficios: Simple deployment, easy debugging, low operational overhead, clear domain ownership

Compensaciones: Cannot scale domains independently, all modules share process, no service layer for reuse

JWT for Authentication

Decisión: Stateless JWT tokens with Authorization: Bearer header

Motivo: Standard for REST APIs, no session storage needed

Beneficios: Stateless, no server-side session store, scales horizontally

Compensaciones: No server-side revocation, tokens valid until expiry even if user is deleted

No Service Layer

Decisión: Business logic resides directly in controllers

Motivo: Simplicity for small project, fewer files to navigate

Beneficios: Fast development, fewer abstractions

Compensaciones: Untestable business logic, code duplication across auth controllers, hard to reuse logic

Cloudinary for Image Storage

Decisión: Menu item images uploaded to Cloudinary CDN

Motivo: Managed service avoids S3/MinIO setup, provides CDN and image transformations

Beneficios: No infrastructure to manage, built-in CDN, free tier available

Compensaciones: Vendor lock-in, external dependency, cost at scale, latency for non-CDN regions

Client-Supplied Order Bill

Decisión: orderBill is sent by the client, not calculated server-side

Motivo: Likely intentional simplification for MVP

Beneficios: Simpler server logic

Compensaciones: Critical security vulnerability — clients can manipulate order amounts

No Request Validation Library

Decisión: Manual if (!field) validation instead of Zod/Joi

Motivo: Simplicity, fewer dependencies

Beneficios: No additional dependency, explicit control

Compensaciones: Inconsistent validation, no type inference from schemas, generic error messages

Pruebas

None installed•0 pruebas unitarias

Qué se prueba

    Cobertura faltante

    • No test framework installed (no jest, mocha, vitest)
    • No test files or test directories
    • No unit tests for controllers or middleware
    • No integration tests for API endpoints
    • No authentication flow tests
    • No database operation tests

    Desafíos clave

    • Diseñar middleware eficiente para autenticación y limitación de tasa
    • Estructurar un manejo de errores consistente en todos los endpoints

    Aprendizajes clave

    • Arquitectura limpia MVC aplicada a servicios Express.js
    • Técnicas avanzadas de indexación y agregación en MongoDB