Private Server Databasing

it depends -> you need good syncing between account/game server (for my txt system, I use Mutex to lock accounts etc. so data gets synced correctly without ever corrupting).
And to be honest, it doesn't matter what database system you use, it's all about how you structure the system (if the system has check more stuff, when more accounts/characters are made, then something isn't right -> the idea is to keep the same performance for reading/writing data, with 1 account, or thousands of accounts)

Similar to what Skilly said. The type of database you use don't really matter, it's more of how you structure and handle your database.

For example making a txt database system IMO is very tedous and annoying (When I made a txt database system for a little project that I did outside the bounds of RotMG Pservers, I found it really annoying to do(was prob due to being an inexperienced coder in general), and I couldn't really figure out a way to keep it organized and simple simple to access), but actually making the database was quite simple.(not rotmg xd)

I made it like this:

redis is the fastest database system.

but horrific to implement

I think I did accept your request, if not, tell me your ******* again :P

speed alone is a horrible metric to judge database systems on, and to be fair just about ANY database system will be able to run "fast" with a low set of data.

if you want a database to be scalably fast, that is, fast even when operating under a large load of entries, you need to know how to design indexes, and how each option of database handles indexes, since those are a world of new ups and downs to deal with.

for example, RavenDb performs indexing work in the background which means that it will always have an index ready for use but the index may produce stale, or out-of-date results.

i wouldn't go so far as to say that NoSQL is better than SQL, because SQL has some strengths that document stores or simple key-value stores simply don't have due to design.

buuut, you said you're not planning on publicizing your server., so like 70% of all database features and caveats don't matter to you. hell, you could even store your data in app memory itself and just flush out to text once in a while

Really any solution should work if you are not expecting a substantial amount of reads/writes. If you aren't looking for scalability, then I'd focus on ease of use. MySQL is simple, or you can look into file system solution recently posted.

For scalability and constant speed, you should look into my favorite, DynamoDB from AWS. It has a good free tier that should fit with most things you'd work with.

Awesome feedback! Thanks!

- - - Updated - - -

Thanks alot m8 I'll be looking into it

- - - Updated - - -
@059 @Ahlwong. My questions have been answered, but there is still room for discussion. I'll be fine with this thread being closed