How to tell if a project needs NoSQL database solution?

by Yevgeniy Afanasyev   Last Updated December 28, 2018 04:05 AM

How to tell if a project needs NoSQL database solution?

Maybe SQL limits define it, if project needs bigger database or bigger fields than it needs NoSQL.

Am I right?

I looked into NoSQL database limits. They are below:

For an example I'm using MongoDB assuming that DynamoDB has similar numbers.

Mongo can be installed on a number of computers/nodes. PostgreSQL does not provide built-in tool for sharding, however citus is around.

MongoDB supports databases up to 64 terabytes and document size is 16 megabytes.

MySQL has a database limit of 256 terabytes, 64TB the maximum size for a table and record limit of 4 gigabytes

PostgreSQL has no limit on database (4 terabytes does exist somewhere for testing) and it has a limit of 1 gigabytes for the size of any one field in a table and again 64TB the maximum size for a table.

Is there anything else that is relevant for decision making process?



Related Questions




Normalisation Vs Join , trade-off

Updated August 24, 2017 19:05 PM

Which PostgreSQL or NoSQL

Updated February 27, 2018 10:05 AM