Conversation

Notices

1. Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 24-Apr-2018 08:51:02 UTC Hallå Kitteh

   • inmysocks Of Doom, Naked KSC
   • Elias Mårtenson
   @loke @inmysocks I have warm fuzzy feelings about CouchDB, but have only played with it superficially.
   
   MongoDB used to have zero guarantees about on-disk consistency ("Well, you should be running a cluster of at least 3 anyway, and then you can just sync it all up when the node comes back!"), but I hear they were supposed to have fixed that 1-2 years ago. Still, the Mongo team doesn't inspire confidence in their priorities. I vaguely remember that defaults are set for optimum benchmarks (no guarantees) and you need to watch out how you configure things in production.
   
   CouchDB is supposed to be rock solid, just deploy and off you go. The only thing to keep in mind is you probably want to schedule compacting if you have a DB that sees a lot of traffic.
   
   I've been meaning to try CouchBase for a long time, that's the first place I'd look if I needed a document db. It still uses Erlang in places, but it has cut away the more visionary and Notes-like parts of CouchDB and focuses on being a plain store rather than a cool, user-replicable data/design/code platform.
   
   
   But yeah, for small things, my gut is with CouchDB.
   
   Even npmjs.com ran CouchDB until recently. I forget what they switched to, and can't find it at a glance. They still offer CouchDB replication for public packages if people want to keep the registry locally.
   • inmysocks Of Doom, Naked KSC (inmysocks@mastodon.social)'s status on Tuesday, 24-Apr-2018 08:14:35 UTC inmysocks Of Doom, Naked KSC

     I am looking at document databases. Has anyone used CouchDB enough to have an opinion of it? I have heard that I shouldn't use MongoDB but I don't know why other than it seems like it takes more to set up.

     I would just be playing with small things so I don't want anything big.

     I am probably just going with CouchDB.

     Hallå Kitteh repeated this.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 24-Apr-2018 09:19:41 UTC Hallå Kitteh

     • inmysocks Of Doom, Naked KSC
     • Elias Mårtenson
     @loke @inmysocks Aha, didn't know that about CDB 2.0, thanks for the update. Didn't know what Mango is either. If it offers a way to lower the threshold of transition to CouchDB, it sounds like a good idea.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 24-Apr-2018 09:21:44 UTC Hallå Kitteh

     in reply to

     • inmysocks Of Doom, Naked KSC
     • Elias Mårtenson
     @inmysocks @loke And I agree, the way views are done is pretty cool. :-)
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 24-Apr-2018 20:19:15 UTC Hallå Kitteh

     in reply to

     • inmysocks Of Doom, Naked KSC
     • Elias Mårtenson
     @inmysocks @loke This anti-MongoDB rant is only 3 years old:
     
     http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 24-Apr-2018 20:21:31 UTC Hallå Kitteh

     in reply to

     • inmysocks Of Doom, Naked KSC
     • Elias Mårtenson
     @inmysocks @loke Apart from CouchDB, don't forget that SQLite and PostgreSQL are pretty good document stores too.
     
     Apparently SQLite even shares a query language, #UnQL, with CouchBase:
     
     https://social.heldscal.la/url/1479394
     
     (or did in 2011 anyway)
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 24-Apr-2018 20:22:02 UTC Hallå Kitteh

     in reply to
     (CouchBase existed in 2011? Man, everything new is so old.)