How tahminator/codebloom works
Project type and purpose
• This is a full-stack web application named CodeBloom.
• Purpose: Track users’ LeetCode activity, rank them on leaderboards, present daily challenges (POTD), send announcements via Discord/email, and allow admin management.
File structure
• Top-level:
• js/… → React + TypeScript frontend (Vite)
• src/main/java/… → Spring Boot backend (REST controllers, service, data layers)
• db/migration → Flyway SQL migrations for PostgreSQL
• infra/Dockerfile, Makefile, .env.example → containerization and deployment
• docs/, .github/ → CICD, tests, docs
• Patterns:
• MVC-style backend: Controllers → Services → Repositories → Models
• Scheduler modules under common/scheduled → background jobs (POTD setter, submission poller, weekly leaderboard)
• JDA integration module for Discord
• External-API handlers: LeetCode API, Email clients, JWT
• Redis client abstraction (SimpleRedis) for caching/session
README
• Confirms tech stack: React + React Query + Mantine + Tailwind on front end; Spring Boot + PostgreSQL + Docker on back end; deployed on DigitalOcean; error reporting via Sentry.
Main components & their interactions
a. Frontend (browser)
• React SPA served via Vite.
• Uses React Query to call REST API over HTTPS.
• Handles routing (React Router), UI (Mantine + Tailwind).
b. Backend (Spring Boot)
• REST Controllers (AuthController, LeaderboardController, etc.)
• Service layer (LeetCodeApiHandler, SubmissionsHandler, ScoreCalculator, Email, JWTClient)
• Data layer (Flyway migrations → PostgreSQL; Repositories wrapping SQL; SimpleRedis cache)
• Scheduler tasks (PotdSetter, SubmissionScheduler, WeeklyLeaderboard)
• JDA module for pushing messages to Discord via Discord API
c. Database & Cache
• PostgreSQL with Flyway migrations
• Redis (via SimpleRedis) for caching sessions or rate limits
d. External services
• LeetCode API for fetching user profile, submissions, POTD
• Discord via JDA (bot for announcements, weekly updates)
• Email providers (Codebloom official, GitHub OAuth)
• Sentry for error reporting
• DigitalOcean (hosting)
Architectural patterns/design principles
• 3-Tier separation: UI (frontend) ↔ API (controllers & services) ↔ Data (DB & cache)
• Dependency Injection (Spring) in backend
• Repository pattern for database access
• Scheduler for CRON-style tasks
• Adapter pattern for external services (LeetCode, Email, Discord)
• JWT-based auth, session persistence in DB
Essential architectural elements to capture
• Client-side UI + state management (React Query)
• API entrypoints + security (JWT, session)
• Business logic (score calculation, POTD, announcements)
• Data persistence (Flyway migrations, schemas)
• Caching layer (Redis)
• Scheduled jobs (POTD, subscription, weekly leaderboard)
• External integrations (LeetCode, Discord, Email, Sentry)
• Infrastructure/deployment (Docker, DigitalOcean)