- Application for a book library (likely registration, browsing, purchase/borrowing).
Prototype and project architecture, showing the complete flow from the database to the user interface:
- Project architecture flow – general overview of the project flow
- System architecture diagrams:
- System architecture diagram – main architecture in SQL Server
- Backend-Frontend pipeline – flow between backend and frontend
- Bookstore app interface – draft of the website interface
- Azure SQL Server → database hosted on Microsoft Azure cloud.
- SQL Server / SSMS (SQL Server Management Studio) → tool for creating and managing tables, queries, procedures, etc.
- Express API → REST API developed with Node.js + Express.
- Postman → for testing API endpoints.
- Middleware → intermediate functions (e.g.: authentication, validation, CORS).
- CORS → allows the frontend (e.g. Netlify) to access the backend hosted on another domain.
- Pipeline → deployment and continuous integration (CI/CD) flow with Azure DevOps or GitHub Actions.
- Netlify → where the frontend is hosted (SPA = single page app).
- Fetch → the frontend accesses API data with
fetch(). - Auth with SPA repo → user authentication in the frontend.
- Auth session cookie → user session saved in a cookie.
- Middleware → where authentication is handled.
- Password + crypto + hash → secure password storage (e.g.: bcrypt, crypto).
- Azure Storage → for saving files (e.g.: book cover images).
- OpenAPI / Swagger → automatic API documentation.
- C#, Razor Pages, MVC, EF Core, WebAPI C# → .NET part (for study or comparison with Node).
- HTTP, OAPI (OpenAPI) → protocols and standards for APIs.
To see the API documentation locally:
- Open a terminal in the project folder.
- Generated the TSOA spec and routes by running
tsoa-all. - Start the development server.
- Open your browser and follow the link for Swagger docs.
npm run tsoa-all
npm run dev- Swagger: Manual setup guide
- Swagger: Automatic setup guide