Loading repository data…
Loading repository data…
MichaelHanz / repository
A custom registration backend for my school's basketball tournament. I'm building this entirely from scratch without relying on Firebase or Supabase to step away from BaaS tools and finally learn how real APIs, databases, and server architectures work under the hood.But obviously due to the time constraint,i will be using AI for the front-end.
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
A custom-built, decoupled backend architecture and registration system designed to handle real-world tournament operations, high-concurrency sign-ups, and strict roster validation for a faculty basketball competition.
Although I am highly proficient in building full-stack applications, relying entirely on Backend-as-a-Service (BaaS) platforms like Supabase or Firebase abstracts away the true mechanics of software engineering. I realized that to be a genuinely capable developer, I needed to understand what happens under the hood.
With my faculty hosting an upcoming basketball competition, I saw the perfect opportunity to bridge this knowledge gap. I built this system to solve a real-world problem while forcing myself to learn the core concepts of true backend architecture. Rather than having participants fill out a basic Google Form, I wanted to challenge myself and build this custom platform in a one-week timeframe.
The Strict Project Constraints:
Ultimately, this project is a critical step in my journey to understand the deeper mechanics of the cyber world. By mastering Python to build a robust, standalone server here, I am laying the architectural groundwork needed to eventually build my own advanced servers, host Large Language Models (LLMs), and transition into AI Engineering.
This project utilizes a strictly decoupled architecture, separating the client-side presentation from the server-side logic to enforce enterprise-grade engineering practices.
To ensure the tournament could begin accepting registrations immediately while I architect the custom backend, the project was split into two deployment phases.
We deployed a temporary BaaS patch to get the application live on the web in under an hour.
addDoc, collection) to securely fire registration payloads across the network.main branch on GitHub, automatically rebuilding and deploying the Vite React app to the edge network within seconds of any code push.With the frontend successfully decoupled and hosted, development is shifting to a separate Git branch (feature/fastapi-backend) to construct the permanent Python architecture, complete with strict Pydantic validation and a structured PostgreSQL schema.