How rajasatyam/dev-tinder-backend works
Dev-Tinder-Backend is an Express API for developer profiles and connection matching. Clients sign up or log in, then use cookie-authenticated profile and discovery endpoints or send and review connection requests; accepted requests appear in a connections listing. The app mounts the route modules and connects to MongoDB before listening. The graph reflects sampled route and model behavior; the README names no further capabilities, and some details of database wiring beyond the shown connector are inferred only as model persistence.
Main entry points: user.model.js User model · app.js Express app · auth.routes.js Auth routes · profile.routes.js Profile routes
Components 14
API entry
- Express app
src/app.js
Identity and profiles
- Auth routes
src/routes/auth.routes.js - User auth
src/middlewares/auth.middleware.js - Input validation
src/utils/validation.utils.js - Profile routes
src/routes/profile.routes.js
Connection workflow
- User routes
src/routes/user.routes.js - Request routes
src/routes/request.routes.js
Data persistence
- User model
src/models/user.model.js - Connection model
src/models/connection.model.js - DB connector
src/config/connectDB.js
Other components
- API client
- MongoDB
- JWT signing
- Password hashing
Connections 26
- API client → Express app: HTTP requests
- Express app → Auth routes: dispatches
- Express app → Profile routes: dispatches
- Express app → Request routes: dispatches
- Express app → User routes: dispatches
- Express app → DB connector: connects through
- DB connector → MongoDB: connects
- Auth routes → Input validation: validates input
- Auth routes → User model: reads and saves
- Auth routes → Password hashing: hashes and compares
- Auth routes → API client: sets auth cookie
- User model → JWT signing: signs tokens
- User auth → JWT signing: verifies token
- User auth → User model: loads user
- Profile routes → User auth: authenticates via
- Profile routes → Input validation: validates updates
- Profile routes → User model: reads and saves
- Profile routes → Password hashing: checks and hashes password
- Request routes → User auth: authenticates via
- Request routes → User model: finds recipient
- Request routes → Connection model: checks and saves requests
- User routes → User auth: authenticates via
- User routes → Connection model: queries connections
- User routes → User model: queries users
- User model → MongoDB: persists user data
- Connection model → MongoDB: persists requests