Skip to content

School Management Backend

api

A modular Express and MongoDB prototype for school administration and website content, with admission resources, student records, academic downloads, and Google Drive file integration.

Client: TalendIT · View client experience

Role
Backend API and school-content service development
Scope
Domain routes and services, MongoDB access, validation, admission-file handling, and shared middleware
Status
Backend prototype with database services; runtime and production readiness unverified

Problem

School websites need to organize admissions, notices, results, and downloadable documents alongside administrative records. These resources need consistent service boundaries and a way to associate stored files with database metadata.

Constraints

  1. C1

    The repository is a prototype; its test command is a failing placeholder and no automated suite is included.

  2. C2

    Database, email, and Google Drive operations require configured external services; they were not executed during this review.

  3. C3

    Access control and file handling need production validation; no school adoption or live availability is claimed.

Architecture

A modular Express and MongoDB prototype for school administration and website content, with admission resources, student records, academic downloads, and Google Drive file integration.

01

HTTP and domain modules

Express composes school resource routes with domain controllers, services, and Joi validation.

02

Database access

MongoDB connection middleware and shared collection helpers support resource operations.

03

Admission documents

The admission-form service uploads files to Google Drive and records file identifiers and links in MongoDB.

04

Shared infrastructure

Request logging, rate limiting, response helpers, and email utilities support the API.

Decisions

D1

Separate school resources into modules

Admissions, academic resources, and site content have separate route and service boundaries so each area can evolve independently.

D2

Keep file metadata alongside domain records

The admission-form service pairs a Drive upload with a database record, making the document and its school-facing metadata addressable together.

D3

Validate resource input at module boundaries

Joi schemas and validators sit alongside the school resource modules, keeping input rules close to the operations that consume them.

Contribution

  • Organized school resources into controller, service, and validation modules.
  • Implemented MongoDB collection helpers and admission-document integration with Google Drive.
  • Added resource-specific Joi validation alongside shared request and response infrastructure.

Outcomes

  • The inspected source includes database-backed service implementations rather than only route placeholders.
  • The prototype provides a reusable structure for school-site resources; deployment behavior and operational reliability remain unverified.
  • Admission-document service code connects file upload results to school-content metadata.

Verified stack

  • JavaScript
  • Node.js
  • Express.js
  • MongoDB
  • Joi
  • Google Drive API

Working through something similar?

Share your challenge, scope, and timeline to start a focused conversation.

Discuss a project