How luisrfuentes54/web-practice works
This repository is a small Express movie API with a WebSocket endpoint. The HTTP workflow is client request → Express app → route dispatch → movie controller → in-memory movie service → JSON response; the API supports listing, lookup by ID, and creation. The entry point creates and listens on the HTTP server, then attaches the WebSocket server to it. The excerpts show these connections; no README or sampled code documents persistence beyond process memory or additional product features.
Main entry points: server.js Express app · index.js Server entry · index.routes.js API routes · movies.router.js Movie router
Components 11
Server runtime
- Server entry
src/index.js - Express app
src/app/server.js - Port config
src/config/enviroment.js
Movie API
- API routes
src/routes/index.routes.js - Movie router
src/modules/movies/movies.router.js - Movie controller
src/modules/movies/movies.controller.js - Movie service
src/modules/movies/movies.service.js - Movie memory
src/modules/movies/movies.service.js
WebSocket
- Socket server
src/app/socketServer.js
Other components
- HTTP client
- WebSocket client
Connections 11
- HTTP client → Express app: sends requests
src/app/server.js - Server entry → Express app: creates server
src/index.js - Server entry → Port config: reads port via app
- Express app → Port config: configures port
src/app/server.js - Express app → API routes: mounts at /api
src/app/server.js - API routes → Movie router: mounts at /movies
src/routes/index.routes.js - Movie router → Movie controller: dispatches requests
src/modules/movies/movies.router.js - Movie controller → Movie service: calls operations
src/modules/movies/movies.controller.js - Movie service → Movie memory: reads and writes
src/modules/movies/movies.service.js - Server entry → Socket server: initializes on server
src/index.js - WebSocket client → Socket server: connects and messages
src/app/socketServer.js