3 ms·

I note the smillie but could you actually expand on that comment for someone who is only really familiar with relational databases? I've recently become intere

by Lio 10y ago

I note the smillie but could you actually expand on that comment for someone who is only really familiar with relational databases? I've recently become interested in using PouchDB (a CounchDB implementation) for syncing offline content between a user's browser and server where the content is based on a set of fixed documents. I believe that MongoDB can provide similar replication tricks. Once on the server I would expect to extract the data from the documents into a relational warehouse database (probably PostgreSQL as it's one of the databases I know best). A document store _seems_ like the right tool for the job but could expand on why something like Mongo or Couch is a bad idea for situations where you're just storing/syncing documents?

elmigranto 10y ago
> why something like Mongo or Couch is a bad idea Couch is fine, other NoSQL is fine. It's just Mongo I don't like: - weak, if any, guarantees on data consistency and safety; - poor API. If you need anything more complicated than `findOne`, there are at least 3 unrelated syntaxes with major differences that are not compatible; - performance is not what marketing team says it is. Even at home JSON turf, Postgres is pretty comparable. If you have data and queries that will benefit from document store, go for it. But don't choose only based on marketing. There are many more rant on the web, I like this one: http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/ http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-ne...
raverbashing 10y ago
Look up on CouchDB problems, several of its customers have given up on it (more than MongoDB it seems) It's not a bad idea, MongoDB has a lot of undeserved hate (some of it deserved, but the minority), however I'm not sure it would do syncing as you want automatically (CouchDB is probably closer out-of-the-box to what you want)

by Lio 10y ago

elmigranto 10y ago

> why something like Mongo or Couch is a bad idea Couch is fine, other NoSQL is fine. It's just Mongo I don't like: - weak, if any, guarantees on data consistency and safety; - poor API. If you need anything more complicated than `findOne`, there are at least 3 unrelated syntaxes with major differences that are not compatible; - performance is not what marketing team says it is. Even at home JSON turf, Postgres is pretty comparable. If you have data and queries that will benefit from document store, go for it. But don't choose only based on marketing. There are many more rant on the web, I like this one: http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/ http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-ne...

raverbashing 10y ago

Look up on CouchDB problems, several of its customers have given up on it (more than MongoDB it seems) It's not a bad idea, MongoDB has a lot of undeserved hate (some of it deserved, but the minority), however I'm not sure it would do syncing as you want automatically (CouchDB is probably closer out-of-the-box to what you want)