jhonnierdlc/proyectbiblioteca-backend

Purpose and Runtime

This repository is a backend API for a library-management domain: users/authentication, clients, books, loans, loan history, fines, and email operations. The runnable application is under biblioteca/; root package files may serve repository-level dependency management.

Primary startup and database entry points:

• biblioteca/index.js

• biblioteca/db.js

• biblioteca/package.json

HTTP Application Boundary

biblioteca/index.js is the application composition point: it should initialize the server, connect infrastructure, and mount the domain route modules. Route files form the external HTTP/API boundary rather than a browser-facing application.

API areas are separated by resource:

• biblioteca/routes/auth.js

• biblioteca/routes/users.js

• biblioteca/routes/client.js

• biblioteca/routes/libro.js

• biblioteca/routes/prestamo.js

• biblioteca/routes/historialPrestamos.js

• biblioteca/routes/multa.js

• biblioteca/routes/email.js

Persistence Layer

biblioteca/db.js centralizes database connectivity. The models in biblioteca/models/ define the persistent library domain and are the boundary between request handlers and the backing datastore.

Core entities:

• Users and authentication identity: biblioteca/models/user.js

• Library patrons/clients: biblioteca/models/client.js

• Catalog books: biblioteca/models/libro.js

• Active lending records: biblioteca/models/prestamo.js

• Historical loan records: biblioteca/models/historialPrestamo.js

• Penalties/fines: biblioteca/models/multa.js

Lending Lifecycle

The principal business flow is loan management. Requests enter biblioteca/routes/prestamo.js, operate on loan and book/client records, and can produce durable lifecycle artifacts:

• Current loan state: biblioteca/models/prestamo.js

• Completed/archived loan state: biblioteca/models/historialPrestamo.js

• Fine state associated with overdue or penalized activity: biblioteca/models/multa.js

The route separation suggests loan history and fines are independently queryable or manageable through biblioteca/routes/historialPrestamos.js and biblioteca/routes/multa.js.

Identity and Client Boundaries

Authentication is isolated from user administration and library-client management:

• Authentication endpoints: biblioteca/routes/auth.js

• User management endpoints: biblioteca/routes/users.js

• Patron/client endpoints: biblioteca/routes/client.js

This distinction allows application operators/accounts (user) and lending participants (client) to evolve as separate domain records.

Request Safety and Error Flow

Shared middleware establishes cross-cutting request boundaries before route logic:

• Object ID validation: biblioteca/middleware/IsValidObjectId.js

• Request validation: biblioteca/middleware/validate.js

• Async error forwarding: biblioteca/middleware/asyncHandler.js

Handlers should validate identifiers and payloads, delegate persistence to models, and rely on the async wrapper for centralized error propagation.

Deployment and External Services

The application is containerized through:

• biblioteca/Dockerfile

• biblioteca/.dockerignore

Environment-specific runtime settings are expected in biblioteca/.env, likely including database credentials/connection details and any email-provider configuration. Email is an explicit external integration boundary exposed through biblioteca/routes/email.js.