CODEWITHSUNDEEP
mysqldatabasenosql
Adam
Adam

Reputation: 1477

How do I move from a relational database and do I need to?

I'm currently building a CRM for a niche industry that can be tailored for the end user. We currently are using a base table for leads and then basically a hacked together combination of tables as a key/value store for any custom fields that might be added.

Each lead in the CRM also has tables for various owners, permissions, access logs, scheduled tasks, and generated contracts/documents.

Currently, everything is stored in a MySQL database but it just seems really messy. I'm thinking of using a NoSQL solution like MongoDB and then using Redis to create any relationships between tables.

Example: I'm thinking of storing the leads and users in a MongoDB database and then using Redis for storing what users a certain lead belongs to etc.

Just looking for some general advice on what the best solution is for this situation as I haven't dealt with NoSQL before.

Upvotes: 1

Views: 190

Answers (1)

zerkms
zerkms

Reputation: 255065

  1. mysql is a great tool
  2. storages is not some stuff that works automagically. For being working well - the great developer needs to implement great schema and great code.

What I wanted to say: if you have some issues now - it doesn't mean that they will disappear once you moved to another database (paradigm, ideology, etc). Even if they moved away - the new ones will come. Nothing happens without hard working.

And especially to big volumes of data and high loaded projects - there is no general advice and silver bullet.

ps:

I'm thinking of using a NoSQL solution like MongoDB and then using Redis to create any relationships between tables.

MongoDB can maintain relations. This is one more argument to not move to the databases you are not well experienced in.

Upvotes: 2

Related Questions