Socket: ✨ Chatroom Join Event Relay

[psychology50]

작업 이유

• When the HTTP API publishes a chat-join event, the Socket-relay server listens to it and sends the message into the chatroom

작업 사항

1️⃣ ChatMessage Redis Key

• The key for each chatroom message follows the format: chatroom:{chatroom_id}:message:{chat_id}
  • key's maximum value = (9 characters(chatroom:) + 19 characters(chatroom_id) + 9 characters(:message:) + 19 characters(chat_id)) * 2 bytes/char = 112 bytes.
  • Given Redis's 512MB key limit (536,870,912 bytes), we don’t need to use a hash algorithm for key compression.
  • While we could abbreviate chatroom to cr to save memory, this only confuses monitoring and is inefficient for memory conservation. Therefore, we will use complete words.

2️⃣ Design

• same as Api: ✨ Implementing Chatroom Join API: A Bounded Context Approach #184
• We need to implement this feature within the socket-relay module. However, as mentioned, the current server has insufficient memory.
• Thus, I have integrated this feature directly in the socket module. In the future, if additional server resources become available, this feature can be transferred to the socket-relay module.

리뷰어가 중점적으로 확인해야 하는 부분

• I checked the application running in the real environment. If you have any questions about the flow, feel free to ask.
• I verified the unit tests in the DAO layer. Let me know if additional tests are needed.

발견한 이슈

• Currently, no validation or exception handling is in the socket place. This topic may need to be addressed in a future update.