Communications and data caching

[axyiee]

Communications and data caching

Table of contents:

• 📰 Summary
• 🎁 The proposed solution
• • RabbitMQ
• • Sockets
• • Communication-based caching
• 🔗 Reference
• 🤷 Final considerations

Summary

We need to find out a good solution for communication between modules, servers and a good way to cache data and keep it always up-to-date.

The proposed solution

RabbitMQ

RabbitMQ is the most widely deployed open source message broker. It is probably the most robust solution for this problem.

Sockets

A alternative to RabbitMQ would be creating our own message broker implementation through TCP sockets. The reason why TCP is better for this specific scenario is because it has lost packet retransmission features, and we wouldn't want to have losses in communications.

Communications-based caching

The communications-based caching is a technique for always having data up-to-date. It would work in the following process:

1. Whenever the player logs into any server, make a request to the web server about the player's data and store it in local cache
2. Save multi server data (global player data, party info, etc.) in the proxy, and pass it to other servers via communications - RabbitMQ
3. Use Redis to store some private info like a JWT key for accessing private web server endpoints
4. Whenever there is some change in the local cache of some server, send a request to the web server updating the data
5. Be able to update the local cache forcibly through communications, and always notify by communications when some data is changed, to be able to change in the local caches

Reference

1. RabbitMQ
2. Redis
3. What is a web server?
4. TCP Packet Retransmission

Final considerations

Suggestions are appreciated for new sections in this issue, or if you have a better idea about how to improve our communications or/and data caching structure, feel free to let us know about it by commenting down below. Thank you for the attention.