Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elaborate on RDMBS vs NoSQL #477

Open
tomasvanrijsse opened this issue Mar 8, 2021 · 0 comments
Open

Elaborate on RDMBS vs NoSQL #477

tomasvanrijsse opened this issue Mar 8, 2021 · 0 comments

Comments

@tomasvanrijsse
Copy link
Contributor

it's not a 'versus' discussion, it's about what data to put in which db.
Most (big) projects these days use both types of DB's in a single project

MySQL is useful for most of the data in all applications. Every application needs to start relational for example with entities like users, companies, subscription etc. Since most of the data we deal with is relational by nature.

NoSQL is useful for:
○ data collection without the time to properly normalize it in advance (e.g. collect log data and user activity without knowing what to do with it)
○ search engines (e.g. ElasticSearch)
○ for caching (you can put all data in a single document, skipping joins and allowing duplicate data)

To bad MongoDB has been hyped and in use for general purposes.
This leads to skipping proper database design and will give trouble on schema changes

It's easy to simply store your JS objects as JSON in Mongo but thats just as easy in Postgress or MySQL.

Some comments from people wishing they never started using MongoDB:
https://www.reddit.com/r/node/comments/8r263o/why_should_i_use_mongodb_and_not_mysql_with_node/#thing_t1_e0pfb21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant