-
Notifications
You must be signed in to change notification settings - Fork 13
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
Measure number of issues corrected by code authors in response to a Discord comment #89
Comments
MongoDB? It's a common choice for Node projects because it stores JSON-like documents. |
I have serious reservations about Mongo. Probably fine to start with, but if usage increases and the stored object complexity goes up, I'd suggest quickly moving to a SQL RDBMS with sequelize. |
In addition, heroku apps all come with a free tier of heroku-provided Postgres. Though there are plenty of good addons for free Mongo dbs too. I had a good experience with MongoHQ. |
Interesting. What are some of the reservations? Not that I doubt you. It's just that people talk about Mongo like it's a given with Node projects. |
It has some fundamental (by design) issues with data integrity, which is the main concern. Apart from that, it's a very code and CPU intensive data store, which can make some operations (data analysis & reporting) much more complicated than SQL alternatives. |
As a former Mongo enthusiast, I've seen the data integrity issues @groovecoder has mentioned. For tracking large things like number of corrected lines, it may not matter as much, but if we use it for things like #79 it could be a problem. I personally have enjoyed both couchdb and postgres over Mongo. |
As per the conversation in #15. Likely would best be done with a database. So what db do we use?
The text was updated successfully, but these errors were encountered: