How andrlime/newdebateapp works
Project type and purpose
• This is a full-stack web application called NewDebateApp.
• Frontend: Next.js + React + Mantine, providing UI for creating evaluations, generating pairings, managing judges and users, etc.
• Backend: A Rust microservice (currently) exposing REST endpoints for data persistence and business logic.
• Serverless: Two Python AWS Lambda handlers (CSV and OO processing) for specialized batch or on-demand tasks.
File structure
• Top-level directories:
• frontend – Next.js pages, UI components, client-side store (Redux-style slices)
• backend – Rust service with Cargo config, Dockerfile, source modules for DB, models, routes
• lambda – standalone Python scripts for AWS Lambda handlers
• Config/deployment: Dockerfiles in both frontend and backend; Rust’s Cargo.toml; Node’s package.json; tsconfig.json
• No infra as code repo here, but the presence of Dockerfiles implies containerized deployment
README for additional insights
• Technology choices: Next.js (no Tailwind) on frontend, Rust on backend, planned rewrite to Java/Kotlin Spring
• Improving maintainability, so clean separation of concerns is key