github-starred/couchdb-best-practices
2
0
Fork 0
mirror of https://github.com/jo/couchdb-best-practices.git synced 2026-05-15 14:16:00 -06:00
Code Issues 232 Projects Releases Packages Wiki Activity Actions

(#3) - Should I use filtered replication?

Browse source
This commit is contained in:
Johannes J. Schmidt 2015-05-05 18:09:03 +02:00
parent 1cb7662b3a
commit 2ead2b6a7a
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -48,6 +48,12 @@ means additional lookups and prevents CouchDB from directly streaming the view
result from disk. But this is negligible. So don't emit the whole doc unless you
need the last bit of performance.
## Filtered Replication
Filtered replication is a great way limit the amount of data synchronized on a
device. But be aware that replication filters other than `_doc_ids` are very slow,
because they run on *every* document. Consider writing those filter functions in
Erlang.
## CouchDB Merge Conflicts
Some things need to and should be conflicts. CouchDB *conflicts are first class
citicens*, (or at least [should be treaded