search

GlowstoneMC / Shine

Glowstone's plugin database
MIT License
3 stars 1 forks source link

Database management #4

Open aramperes opened 7 years ago

aramperes commented 7 years ago

We should decide which database platform(s) we want to support. I would personally prefer a NoSQL solution (MongoDB, Redis, etc.), but using an SQL solution could also have its benefits.

It would have to cover user management (including registration, permissions, profiles and authentication) and social interactions (comments, reviews, etc.), as well as moderation (approval of files, bans, etc.)

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/45425272-database-management?utm_campaign=plugin&utm_content=tracker%2F45742928&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F45742928&utm_medium=issues&utm_source=github).
gdude2002 commented 7 years ago

Mongo has a lot of stupid defaults and historical issues; it might be worth looking at because of the BSON but otherwise I wouldn't really recommend it. Redis is not suitable.

You are almost certainly better off with something like postgresql and an ORM - you're going to need the structure and strict enforcement that a relational database forces on you.

picknchew commented 7 years ago

:+1: for Mongo

mastercoms commented 7 years ago

I'd like Postgres or Mongo, but prefer Mongo.