3 ms·

https://twitter.com/nodejitsu/status/321775765962240000 https://twitter.com/nodejitsu/status/321775765962240000 "Sorry for the inconveniences, we found that ou

by seldo 14y ago

https://twitter.com/nodejitsu/status/321775765962240000 https://twitter.com/nodejitsu/status/321775765962240000 "Sorry for the inconveniences, we found that our database provider (@IrisCouch) is down at the moment, we are bringing up the cloud." I'm pretty surprised to learn that they don't run their own databases (and also that their database is CouchDB, but maybe I'm just old fashioned).

film42 14y ago
My two cents: CouchDB is great in that it allows you to remove the backend and rely solely on a database with REST baked in. However, it has its drawbacks, like database queries can be costly do to transactions over http. It's like every other argument in the community, how much control over ease do you want?
- sendob 14y ago
  So you think these drawbacks are in someway related to the fact that they are offline? It seems like you are just jumping for a chance to kick a project and or spread some FUD. Not to mention "database queries can be costly do to transaction over http" => Not gonna get into this too much, but couchdb has an optimistic concurrency model, yeah? An implementation that uses a technology ( or like iriscouch is a db as a service) is not that technology. If heroku postgresdb's go down because they configure things incorrectly is that the fault of the project? Could be, could be documentation was lacking, or it was a real footgun. It is also possible to deploy technology within a budget where failures are the expected outcome, it is also very possible to deploy technology in a manner which does not support a use case, or may not even be something the technology can support, that does not make it 'bad' or 'great', and has nothing to do with "control vs ease" or http vs a yet to be named wire protocol... I just don't see how this is helpful, accurate, or adds to the discussion, sorry if I am jumping down your throat about it.
  - film42 14y ago
    You are a bit, but that's ok, fwiw, I'm speaking from my experience whether it's right or wrong, which I felt had value. I only meant that after using it on several projects, I felt that it had some cool features, but there are quite a few 'gotchas' that come with it. That is, come with thinking it's like any other database, which it's not.

by seldo 14y ago

film42 14y ago

My two cents: CouchDB is great in that it allows you to remove the backend and rely solely on a database with REST baked in. However, it has its drawbacks, like database queries can be costly do to transactions over http. It's like every other argument in the community, how much control over ease do you want?

sendob 14y ago
So you think these drawbacks are in someway related to the fact that they are offline? It seems like you are just jumping for a chance to kick a project and or spread some FUD. Not to mention "database queries can be costly do to transaction over http" => Not gonna get into this too much, but couchdb has an optimistic concurrency model, yeah? An implementation that uses a technology ( or like iriscouch is a db as a service) is not that technology. If heroku postgresdb's go down because they configure things incorrectly is that the fault of the project? Could be, could be documentation was lacking, or it was a real footgun. It is also possible to deploy technology within a budget where failures are the expected outcome, it is also very possible to deploy technology in a manner which does not support a use case, or may not even be something the technology can support, that does not make it 'bad' or 'great', and has nothing to do with "control vs ease" or http vs a yet to be named wire protocol... I just don't see how this is helpful, accurate, or adds to the discussion, sorry if I am jumping down your throat about it.
- film42 14y ago
  You are a bit, but that's ok, fwiw, I'm speaking from my experience whether it's right or wrong, which I felt had value. I only meant that after using it on several projects, I felt that it had some cool features, but there are quite a few 'gotchas' that come with it. That is, come with thinking it's like any other database, which it's not.