RACOON-IN-THE-HOLE

A proven framework for enterprise-grade web applications, offering excellent REST API and WebSocket/STOMP support along with a rich ecosystem and stability. Particularly effective for implementing authentication/authorization systems through Spring Security and efficiently managing thread pools for concurrency control.

In multiplayer games where real-time bidirectional communication is essential, WebSocket provides low latency and persistent connections. By utilizing the STOMP protocol, we implemented a topic-based pub-sub pattern, enabling granular message broadcasting at Room/Game/Player/Team levels. We secured the system by applying token-based authentication to STOMP headers.

Relational database for reliably storing and managing structured data such as user information, room data, and match history. Ensures data consistency through transaction support and provides fast query performance through indexing.

Utilized Java's concurrent collections and Executor framework to implement safe and efficient asynchronous request processing in a multithreaded environment. Built a thread-safe task queue using ConcurrentQueue and optimized CPU resources through Thread Pool to achieve high concurrency.

A JavaScript framework specialized for browser-based game development, simplifying complex game logic such as rendering, physics engine, and input handling. Provides friendly pixel art graphics and can be integrated with WebSocket to visualize server game states in real-time.

Built an asynchronous request processing system using Java's ConcurrentQueue and Thread Pool. Separated game logic from network I/O to eliminate bottlenecks and optimized CPU resources through thread pools, enabling stable handling of 300+ concurrent users.

Adopted event-based updates instead of frame-based updates, significantly reducing network traffic. Optimized to selectively broadcast only to necessary players on game state changes, achieving p95 latency of 50ms.

Optimized query performance through execution plan analysis when developing match history aggregation and statistics systems. Improved bulk data query performance by adding appropriate indexes and resolved performance issues of offset-based pagination by applying cursor-based pagination.

Utilized MySQL's MVCC (Multi-Version Concurrency Control) and transaction isolation level (READ COMMITTED) to ensure data consistency during concurrent game state updates. Implemented distributed concurrency control by appropriately combining optimistic and pessimistic locks.

Implemented a token-based authentication system using JWT (JSON Web Token). Enhanced security by adding token expiration times and refresh token mechanisms, and performed authentication during WebSocket connections by including tokens in STOMP headers.

Introduced a Server-Authority model where all game logic is processed on the server to prevent client manipulation. Clients only send inputs, and the server calculates all game states to ensure the same game state for all players.

Centralized game logic management through the Server-Authority model maintained consistent game states even when multiple clients sent simultaneous requests. Achieved p95 latency of 50ms by minimizing network load through event-based broadcasting and selective message delivery.

It was a valuable learning experience to implement various technologies including randomness algorithms, state machines, token-based authentication, and asynchronous processing within a single project.

In the process of focusing on technical implementation and performance optimization, we lacked consideration for the originality of gameplay mechanisms or differentiation of user experience.

We failed to clearly define the core fun elements and differentiation points of the game early on, and lacked a process to collect user testing and feedback from the beginning of the project.

In the game planning stage, I will ask 'Why would this game be fun?' and invest more time in competitor analysis and gameplay loop design.

Before selecting the tech stack, I would like to apply a 'gameplay-centered development methodology' that first defines the core fun elements and then selects optimal technology accordingly.

I will conduct playtests with acquaintances from the prototype stage and create a continuous improvement cycle by introducing metrics to quantitatively measure 'fun'.