A slug is an alternative to a name that would otherwise not be acceptable for various reasons – e.g. containing special characters, too long, mixed-case, etc. – appropriate for the target usage. What target usage means is context dependent, but could include usage in a URL or name of a file or database table for … Read more
Unfortunately there is no detailed documentation describing the replication protocol. There is only the reference implementation built into CouchDB, and Filipe Manana’s rewrite of the same which will probably become the new implmentation in the future. However, this is the general idea: Key points If you know Git, then you know how Couch replication works. … Read more
Don’t let the spatial scale (1000+ devices) mislead you as to the computational and/or storage scale. A few dozen 35-byte inserts per second is a trivial workload for any mainstream DBMS, even running on low-end hardware. Likewise, 142 million records per month is only on the order of 1~10 gigabytes of storage per month, without … Read more
First you put the user in _users database. The ID of the document must be org.couchdb.user:username, e.g. With CouchDB 1.2.0 or later use this: { “_id”: “org.couchdb.user:dbreader”, “name”: “dbreader”, “type”: “user”, “roles”: [], “password”: “plaintext_password” } CouchDB will hash & salt the password for you on the server side and save the values in the … Read more
CouchDB is a document store. You put documents (JSON objects) in it and define views (indexes) over them. The objects can be arbitrarily complex with potentially deep structure. Further, they are not constrained to following some consistent schema. Cassandra is a ragged-table key-value store. It just stores rows, each of which has a set of … Read more
When getting started, do not use CouchDB libraries in NodeJS! There several, however they are largely thin layers wrapping the HTTP API. But Node has very strong HTTP support. It’s no more trouble to make simple HTTP queries. It’s simpler. It’s less prone to errors. When CouchDB adds a feature, you won’t need to wait … Read more
You need to think of how you approach the application in a document oriented way. If you simply try to replicate how you would model the problem in an RDBMS then you will fail. There are also different trade-offs that you might want to make. ([ed: not sure how this ties into the argument but:] … Read more
No. CouchDB uses an “optimistic concurrency” model. In the simplest terms, this just means that you send a document version along with your update, and CouchDB rejects the change if the current document version doesn’t match what you’ve sent. It’s deceptively simple, really. You can reframe many normal transaction based scenarios for CouchDB. You do … Read more
I’m not sure if this is what you’re after, but from what I understand you’re looking for the [JsonIgnore] attribute. Stops properties from being serialized with the rest of the object into to JSON. [JsonIgnore] public string Whatever{ get; set; }
The main differences are the data model and the querying capabilities. Key-value stores The first type is very simple and probably doesn’t need any further explanation. Data model: more than key-value stores Although there is some debate on the correct name for databases such as Cassandra, I’d like to call them column-family stores. Although key-value … Read more