4 ms·
Why MongoDB for what is pretty much a front-end :( What's wrong with SQLite?
by StavrosK 10y ago
Why MongoDB for what is pretty much a front-end :( What's wrong with SQLite?
- Terretta 10y agoMore front-endy, see Dashing, now Smashing, a Sinatra based framework that lets you build beautiful dashboards. https://github.com/SmashingDashboard/smashing/wiki https://github.com/SmashingDashboard/smashing/wiki You can store models in SQLite: https://github.com/SmashingDashboard/smashing/wiki/How-To%3A-Define-a-data-model-and-store-history-data-to-database https://github.com/SmashingDashboard/smashing/wiki/How-To%3A...
- dom0 10y ago"The path of MongoDB is often the same: first the primary DB, then the configuration store, then it's finally removed" - (friend of mine)
- 77pt77 10y agoSolving imaginary scaling issues at scale. http://img.pandawhale.com/post-73940-Solving-Imaginary-Scaling-Issu-FA3D.jpeg http://img.pandawhale.com/post-73940-Solving-Imaginary-Scali...
- wehadfun 10y agoExpand. MongoDB is finally removed? Why?
- shawabawa3 10y agoI think the implication is that mongo is picked because it's "cool", and eventually everyone realises another tool does the job better (e.g. regular sql database/redis/sqlite/etc)
- brettmiller 10y agoI was the eng manager when we started this project... so why Mongo? - baumandm suggested Mongo and it seemed to meet all of our requirements. - We started the project in May 2013. Mongo was a lighter weight / simpler solution back then. - We were building dashboards for monitoring systems (like grafana) and we wanted high availability of our data store. - The dashboards are defined with a single JSON document, but the JSON is dynamic for every dashboard. I'm no longer involved in the project, but Mongo is probably still a good choice.