What is the currently best solution to save persistent data in a way that it can easily be accessed by all servers in the backend?
I know that SQL should not be used to save persistent data but what would be the optimal way? Running on Velocity, 1.21.8. I cant find a really good solution other than sql, can you? Would be cool to have a FlaggableObject which is shared between all servers or so xD
#Best solution for proxy wide persistent data?
14 messages · Page 1 of 1 (latest)
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
Depending on what the information is, but generally if you're trying to access information across multiple servers a DB is fine
An SQL based one, Mongo, whatever you prefer
That warning is mostly for storing data that doesn't really need a DB (which is most use-cases usually)/on single server setups, e.g. if you replaced - flag <player> abilities:fire|ice with full SQL storage, that'd be a bit overkill and not needed in most cases
So I can just ignore that? "This commands exists primarily for interoperability with pre-existing databases and external services.
It should never be used for storing data that only Denizen needs to use. Consider instead using Command:flag." from https://meta.denizenscript.com/Docs/Commands/sql
So as long as it is something I need on multiple server its fine? I know about 2-4 years ago I asked here something about it (also multi server setup) and mcmonkey was like "NEVER USE SQL", so just wanna be sure if there is a better solution now xD Of course if not needed i am also always using flags ^^
Command search for 'sql'
It depends, you could also use the bungee integration and move the data across yourself if you're on Bungee, but that just depends on what sort of data, the frequency of moving it, when it's needed, etc.
Yea i do that on my bungee setup, but this is another server where velocity is used, so thats not working xD
DBs are very common practice, they're just often overkill as opposed to the systems Denizen already has to manage data which are easier to use - nothing is inherently bad always, just depends on being the right use-case
okay dokay, thanks for that, than I will do that 🙂
For a velocity setup where you need to move data across servers, I'd say a DB makes sense - kinda falls under the data that only Denizen needs to use bit, as you're sending it across a proxy and to at the very least different servers & instances of Denizen
No problem :p, feel free to ask if you need any more help, otherwise -
Thread Closing Reminder
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@arctic flame