3 ms·
If you are doing document processing, a document database is actually the right choice. I disagree with your comment. I do machine learning and NLP, and I pref
by bravura 16y ago
If you are doing document processing, a document database is actually the right choice.
I disagree with your comment. I do machine learning and NLP, and I prefer mongodb as a data-store to RDBMs. SQLite would be overkill. MongoDB is a more convenient and simple choice than an RDBM.
Using a schema-less document database is natural in NLP, where you might add columns to your fields on the fly, e.g. you are experimenting with a new preprocessing step and want to cache the result.
- houseabsolute 16y agoI'm curious what you mean by "overkill." SQLite has really low startup costs and is easy to use from almost any language. The code you have to use to query it is not verbose. Typically when I see the word "overkill," I expect that there is some downside for using an approach that is too powerful. But I can't think of a downside to using SQLite in this context.
- jpcx01 16y agoSQLite requires schema definition (CREATE TABLE, ALTER, etc). Thats a bit overkill sometimes when you just want to store a JSON object. Mongo makes it much easier to just start pushing data into collections without having to worry about the tables and columns being defined.