How jjoonior/pading works
Project type and purpose
• This is a full-stack, real-time collaborative coding platform (“Pading”) with features for pair programming: group/project management, chat, video conferencing, shared IDE (Monaco+Yjs), terminal (Xterm.js+STOMP), auto-build/deploy, resource monitoring, AI code review.
• The front-end is a React/TypeScript single-page application (Vite, Tailwind). The back-end is a Spring Boot monolith using REST and STOMP over WebSocket, backed by a relational database, Redis, and Kubernetes.
File structure
• front-end/: React components organized by feature (groups, projects, chat, videochat, file explorer, editor, monitoring). Uses Redux for global state and context for editor.
• back-end/: Spring Boot with layered packages (config, controller, service, repository, entity, aop, interceptor). Config includes WebSocketConfig, RedisConfig, KubernetesConfig, OAuth2Config, JWT filter.
• exec/sql/: database DDL for entities (User, Group, Project, Chat, etc.).
• Dockerfile and CI config present; Kubernetes utilities exist in code (KubernetesUtil).
README for additional insights
• Stack: React+TS, Tailwind, Vite; Spring Boot, Gradle, Docker, Kubernetes, Redis.
• Key real-time tech: WebSocket/STOMP (chat, terminal), Yjs for CRDT editor sync, OpenVidu for video, AI code review via external API, Kubernetes orchestration for per-project containers.
a. Main components
• Client (Browser): React SPA, Monaco Editor + Yjs client, Xterm.js terminal, STOMP/SockJS client, OpenVidu JS.
• API Gateway / Web Server (optional Nginx): serves SPA assets, routes API & WebSocket.
• Backend (Spring Boot):
• REST controllers: AuthController, GroupController, ProjectController, etc.
• WebSocket endpoints: STOMP endpoints for chat, terminal, Yjs signalling.
• Kubernetes Controller: spins up project containers via Kubernetes API.
• Redis: session or cache for JWT blacklists, ephemeral data.
• Database (MySQL/Postgres): persistent storage for users, groups, projects, chat logs.
• OpenVidu signalling: interacts with OpenVidu Server.
• Kubernetes Cluster:
• Project Pods/Containers: build & runtime containers per project.
• Nginx Ingress / Service Mesh.
• OpenVidu Server: video conferencing media server.
• External OAuth Providers: Google, Kakao.
• AI Code Review Service (external API).
b. Relationships & interactions
• User → Browser SPA → REST API (JWT/OAuth2) → Backend → Database/Redis.
• Browser ↔ WebSocket (STOMP/SockJS) ↔ Spring Boot WebSocketConfig → ChatService/TerminalService/Yjs SignalServer.
• Spring Boot → Kubernetes API → create/delete project containers → container IPs.
• Browser terminal & editor connect directly (via STOMP) to their project container endpoints or WebSocket proxy.
• Browser ↔ OpenVidu Server (session join, media streams).
• Backend → AI service (HTTP) for code review.
c. Architectural patterns & principles
• Layered MVC (Spring Boot layers: controller → service → repository).
• Event-driven & message-oriented for real-time features (STOMP topics).
• CRDT synchronization pattern via Yjs.
• Micro-VM/container per project for isolation.
• OAuth2 + JWT for stateless, scalable auth.
• Kubernetes for orchestration, auto scaling.
d. Key technologies/frameworks
• Frontend: React, TypeScript, Vite, Tailwind, Redux, Monaco Editor, Yjs, Xterm.js, STOMP.js, SockJS.
• Backend: Spring Boot, Spring Security (OAuth2, JWT), Spring WebSocket, Redis, JPA/Hibernate.
• Orchestration: Docker, Kubernetes API.
• Media: OpenVidu.
• Database: MySQL/Postgres (JPA).
• Cache: Redis.