4 ms·
Saying a document database is the same as a JSON field is a bit reductive. I think you chose this instead of MongoDB like you would chose SQLite instead of MSS
by jermaustin1 4y ago
Saying a document database is the same as a JSON field is a bit reductive.
I think you chose this instead of MongoDB like you would chose SQLite instead of MSSQL. The library is very similar to Mongo's .Net library, so its almost a 1:1 code replacement.
- nordsieck 4y ago> I think you chose this instead of MongoDB like you would chose SQLite instead of MSSQL. The library is very similar to Mongo's .Net library, so its almost a 1:1 code replacement. I guess it depends on what's important. Some people primarily care about the API. Other people focus on the operational story.
- quickthrower2 4y agoI agree. The way I see it, a document DB (I have used Firebase) has features that make it nicer to work with documents. For example Firebase let's you query and index based on the data within the "JSON" (in quotes because it is not really represented in Firebase as JSON, but is close in structure). Another thing is you might want the lack of features. I.e. you want it so people don't do joins etc. Because you want the team to use the same paradigm with local data as with server hosted. I can think of reasons why.
- JamesSwift 4y agoSQLite lets you do those JSON things as well.
- RedShift1 4y agoYou can create an index based on expressions so you can index fields inside JSON data with sqlite.