Master application to handle data of micro applications

[PedroMPagani]

Hey, I'm writing an application based off of 3 events,
User connect, user reconnect, user disconnect.

Basically user reconnect means connecting to another microservice, user connect can be connected to any microservice and user disconnect means not using any of the applications anymore.

These microservices are Minecraft servers, we got to a point of 1000 concurrent players online and we're currently handling data this way:

Load data from MySQL db once the user connects to any microservice, which means that we're loading from database again and again when he connects or reconnects, and saving data constantly to the database too.

I've been trying to desing a model where we would have some sort of central container to store that data, with a more fast access than loading the MySQL database all the time, as well as executing updates to it, and instead transferring all this data through the redis pubsubs, and also updating it in the pubsubs too, or maybe caching that data once first loaded into redis and then updating again and again and in the end execute the update in the MySQL database on user disconnect.

Does anyone have any thoughts on this? Sounds like a bad or good model? Any suggestions?