Digital Library Management System

Overview

The goal was not only to build a library application, but to experience a more complete software-development lifecycle. The system covers registration, book management, borrowing, returning, authentication, and reporting.

Five Scrum sprints made incremental delivery and engineering process part of the problem.

Inputs & Constraints

• Student and staff registration
• Authentication and authorization
• Book search management borrowing returning and overdue handling
• Relational and document-oriented data
• Multi-person team coordination

Approach

The application uses a layered architecture to separate presentation, application logic, persistence, and supporting services.

React provides the frontend, .NET handles core backend functionality, and FastAPI supports authentication-related services. PostgreSQL stores relational data, MongoDB holds document-oriented records and logs, and Docker packages services.

OAuth 2.0 concepts and two-factor authentication inform the authentication workflows. Backend APIs and user-facing workflows were validated with Postman and structured manual testing across five Scrum sprints.

Outcome

The final system covers the primary workflows expected from a university library application and organizes several technologies within one architecture.

Its main outcome was exposing the process around software itself: changing requirements, integration boundaries, testing responsibilities, coordination, and maintaining architecture as functionality evolves.

What I Learned

• Layered architecture and API boundaries
• Authentication and authorization
• SQL and NoSQL persistence
• Testing workflows
• Scrum-based delivery
• Integrating services built with different frameworks

Practical Application

• University administration systems
• Inventory applications
• Document-management systems
• Membership platforms
• Lending systems

Tech Stack

• .NET
• FastAPI
• React
• PostgreSQL
• MongoDB
• Docker
• Postman