|
mongo changed their license so that aws couldn't use them. amazon responded by just reimplementing mongo
|
# ¿ Jan 14, 2019 22:07 |
|
|
# ¿ May 17, 2024 21:52 |
|
i love to have my schemas defined implicitly by the code using the data so that i can never be quite sure what fields should be present
|
# ¿ Jan 15, 2019 05:43 |
|
abigserve posted:I would also like to know what the downside of doing this is for small document stores the downside is that most filesystems are sort of shockingly bad at reliably storing data. with postgres you can safely assume that if you insert a row, subsequent queries will either not see that row or will see the complete row that you inserted. doing this with a filesystem requires an akward dance of writing to a temporarily file, fsyncing it (and then calling the non-portable real fsync for your platform that actually works) and then moving it to the final location and praying that moves are actually an atomic operation.
|
# ¿ Jan 15, 2019 23:10 |
|
suffix posted:defining a schema is a-ok but managing schema changes gets tired quickly writing code that deals with objects with a bunch of different shapes because you didn't migrate the existing data to the new schema is pretty tiring too
|
# ¿ Jan 16, 2019 00:16 |
|
lancemantis posted:does this mean people running ubuntu in prod will feel vindicated? no, if they were running a proper server os they'd be free from mongo
|
# ¿ Jan 16, 2019 20:28 |