Re:MongoDB 6 Released
by gqewogpdqa on Thursday July 21, 2022 @02:27PM
(#32182943)
>>>MongoDB also provides single document atomicity.
And multi-document, in sharded clusters. 2018: https://www.mongodb.com/blog/post/mongodb-multi-document-aci...
>>>But in RDBMS you can configure the ACID properties. https://www.mongodb.com/docs/manual/reference/write-concern/
Re:MongoDB 6 Released
by hardwaresofton on Wednesday July 20, 2022 @04:50AM
(#32163093)
> I agree with that. For me, the order would be: 1. Do not use database 2. Use SQLite 3. Use single instance RDBMS 4. Use single instance NoSql 5. Use single instance RDBMS + NoSql cluster 6. Use RDBMS cluster
Yeah it’s so funny, HN seems to rediscover way of thinking every so often! I think it’s why SQLite projects are so popular (and of course how well built and popular SQLite is)
Yes, most of NoSql provides some kind of ACID guarantees, however not as good as RDBMS. MongoDB also provides single document atomicity. But in RDBMS you can configure the ACID properties.
> but I want to note that the vast majority of apps do not have data too large to be held by a single instance
I agree with that. For me, the order would be: 1. Do not use database 2. Use SQLite 3. Use single instance RDBMS 4. Use single instance NoSql 5. Use single instance RDBMS + NoSql cluster 6. Use RDBMS cluster
> I'd argue that you should default to OLTP and only deviate when you need the extra power, but we'd probably agree to disagree there :)
Personally I would prefer NoSql when the business model fits some specific patterns. But I agree with you that.
The article of Highscalability.com is very useful, and also some other articles. I did not know the site before, thanks for sharing.