[MC-Plugins] Redis or SQL

[Superbility]

Recently I've seen a lot on Minecraft servers switching from SQL to Redis as their preferred data storage. I was wondering if it would be beneficial to add Redis as a data type to my plugins

 

[ghooslyDev]

Actually, I using Redis for seperate something with network. Like bungee announce, /joinme command, /staffchat and more. If you ask me what is better, my answer is MongoDB. MongoDB is faster than SQL and atleast more easy to use.

 

[Brandon]

Redis is primarily used for communication between servers, not necessarily data storage.
SQL is good for specific things (as long as you're using HikariCP data pooling for speed and efficiency) - although the downside of SQL is that it's mainly flatfile databases.
MongoDB is a good alternative, using json documents to store data.

 

[ghooslyDev]

Yessir

Redis is primarily used for communication between servers, not necessarily data storage.
SQL is good for specific things (as long as you're using HikariCP data pooling for speed and efficiency) - although the downside of SQL is that it's mainly flatfile databases.
MongoDB is a good alternative, using json documents to store data.

 

[Great_Array]

Personally I stick to originals, so between Redis and SQL I prefer SQL, purely because I'm used to it from web development. But it does depend on you, if Redis suits your needs more use Redis, if MongoDb suits you more use it or if even MariaDb suits you use that. But if you're looking to ease the use for your plugins stick with SQL since as far as I know its the most widely used database system out there. Or if one day you just get sick of it all just say heck it and stuff it all in a .txt file!

 

[mella]

I do prefer MongoDB, I have the feeling is easier to use, especially because its object oriented.

 

[_Souper_]

You could use Redis to cache your query results from SQL/MongoDB. Redis has an automatic way to set an expiry so all you really have to do is check if a key exists, if it does return the value of it and if it doesn't do your expensive query, set your key and return the query result. So, i wouldn't personally really put them side by side in a poll.

 

[Inviss]

MySQL should be used if you need to store data that is consistent, like the values of a profile of a player. This is the typical use case. This is because MySQL stores data in tables which contain different columns, which are pre-defined and can not be changed after creation. Although migrating to a different database to add more columns is possible, it's an absolute pain.

This sometimes makes MongoDB the preferred choice of database. Being a NoSQL database means that is you are able to store whatever information you need in each document inside of a collection (equivalent to a table in MySQL). This makes adding new features easy, a simple if database contains check.

Redis, on the other hand, does not store any persistent data. It is an in-memory key-value store. When the redis instance is shit down / the redis pool is closed, all data currently held in it is lost. It's used as it's a super quick and efficient way of syncing data across servers. Say for example you've got a JsonObject that contains a few different properties, and you want to store that JsonObject in a map/list on multiple server instances, you could use redis to "publish" that data, so that it's received by all servers and can be stored/used.

Hope that cleared it up a bit!