How lucas-p-souza/bibliotech works
Project type and purpose
• BiblioTech is a RESTful backend API for library management, written in Node.js/TypeScript with Express and Prisma, using PostgreSQL as its data store. It does not include a UI, but is consumable by HTTP clients (Swagger UI, REST clients, front-end apps, etc.).
File structure
• Top-level folders:
• prisma/ – database schema, migrations, seed script
• src/ – application code, subdivided into controllers, middlewares, models (Swagger schemas), repositories, routes, domain entities and enums, plus the entry point (index.ts)
• http/ – sample HTTP calls for testing via VS Code REST Client
• Key config files: tsconfig.json, package.json, .env (not committed), Docker run for PostgreSQL
• Architectural patterns:
• MVC-style separation – routes → controllers → repositories/domain
• Layered architecture – HTTP layer, application layer (controllers, middleware), domain layer (entities/enums), data access layer (repositories + Prisma), persistence (PostgreSQL)
README for additional insights
• Confirms technologies: Express, TypeScript, Prisma ORM, JWT for auth, bcryptjs, Swagger
• Describes key flows: authentication, role-based authorization, CRUD for books/authors/categories/publishers, future loan/reservation features
• Mentions Docker for DB and Swagger UI
Elements
• HTTP layer = blue
• Application layer (routes/controllers/middleware) = green
• Domain layer = orange
• Data layer (repositories/Prisma) = purple
• External services (DB, JWT) = gray
Detail
• Middleware flows (auth checks) and where JWT validation occurs
• Where the Prisma Client is generated (prisma schema → client) and how migrations/seed fit in