After a second thought, using an in-memory list to store all matching requests isn't an ideal solution. Especially in terms of scalability, the memory holding the list might explode. Its working so far as we have limited connections haha š.
Sry for the last min patch.
Changes Made
Replace list in matching service to RabbitMQManager, an adapter for rabbitmq.
Add rabbitmq to docker compose.
Add rabbitmq to aws stack.
Update gh actions to deploy rabbitmq.
Patch matching lobby UI.
Screenshots (if applicable)
Checklist
[x] I have checked that the changes included in the PR are intended to merge to master or any destination branch.
[x] I have verified that the new changes do not break any existing functionalities, unless the new changes are intended and have approved by the team.
[x] I will take care of the merging and delete the side-branch after the PR is merged.
Additional Notes/References
Use docker compose if you want to setup everything locally, will save the hassle to setup RabbitMQ.
You can access the local RabbitMQ management website at localhost:15672. login and password is guest by default.
the development site has the latest changes using RabbitMQ for matching service.
Pull Request
Description
After a second thought, using an in-memory list to store all matching requests isn't an ideal solution. Especially in terms of scalability, the memory holding the list might explode. Its working so far as we have limited connections haha š.
Sry for the last min patch.
Changes Made
RabbitMQManager, an adapter for rabbitmq.Screenshots (if applicable)
Checklist
masteror any destination branch.Additional Notes/References