How cloud-native-group-1/leave-n-attendance-system-backend works
Project type and purpose
• This is a backend-only service for a Leave and Attendance Management System.
• Built as a modular, containerized, API-centric microservice using FastAPI, it exposes REST endpoints for a frontend or other clients.
File structure
• Top-level artifacts:
• Dockerfile, docker-compose.yaml → containerization setup for the FastAPI app and PostgreSQL.
• alembic.ini and migrations/ → database migration management.
• app/ → the FastAPI application code.
• Inside app/:
• config.py, database.py, t_db.py → configuration and database connection setup.
• models/ → SQLAlchemy ORM models representing DB tables.
• schemas/ → Pydantic models for request/response validation.
• crud/ → data-access layer functions that encapsulate SQLAlchemy queries.
• routes/ → API routers mapping HTTP endpoints to CRUD operations.
• utils/ → shared helpers (authentication, dependency injection).
• tests/ → unit tests for core functionality.
README insights
• Confirms FastAPI + Uvicorn ASGI stack, SQLAlchemy ORM with PostgreSQL, Pydantic schemas, Docker for containerization, Alembic for migrations, and GCP App Engine for deployment.
• Emphasizes clean architecture: separation of concerns across routes, schemas, CRUD, and models.