How kw-classlog/classlog works
Project type and purpose
• This is a full-stack, data-driven online lecture management platform.
• Front-end: Next.js/React PWA handling student/teacher UIs.
• Back-end: Spring Boot monolith exposing REST endpoints, performing business logic (user, classroom, lecture, quiz, notifications).
• Infrastructure: MySQL for relational data, Redis for cache/session, AWS S3 for file storage, external LangChain AI integration, JWT-based security.
File structure for architectural cues
• Top-level “frontend” folder holds the Next.js app, organized by routes (student/teacher/non-login) plus shared components, API wrappers, state stores (Zustand).
• Top-level “backend” folder is a Spring Boot service: domain packages (user, classroom, lecture, lectureNote, quiz, notification, etc.), global cross-cutting concerns (security, exception handling, Redis config, S3 config), and an infra/langchain client.
• Dockerfile and docker-compose.yml in backend suggest containerization of the service and local orchestration with dependent services (MySQL, Redis).
Key insights from the README
• Back-end tech: Spring Boot (Java 17), MySQL, Redis, AWS S3.
• Front-end tech: Next.js (TypeScript), React, Zustand, SCSS, PWA.
• CI/CD/Deployment on AWS (but not detailed here).
• Business features: user sign-up/login (JWT + Redis), class & lecture management, quiz generation & analysis (with AI), notifications and settings, file storage for lecture materials.