CouchDB同步是否向所有用户复制数据库？PouchDB过滤复制咨询

Great question—this is exactly the use case filtered replication was built to address! Let’s break this down clearly:

First, your initial concern #

By default, a standard PouchDB sync will replicate the entire remote database to every local device. That’s obviously a non-starter for a chat app where users shouldn’t access other people’s conversations. Filtered replication fixes this by letting you restrict exactly which documents get synced.

How filtered replication works #

At its core, filtered replication uses a filter function that runs on the remote database (almost always CouchDB, since PouchDB’s sync is designed to pair with it). Here’s the step-by-step flow:

• When your local PouchDB initiates a sync, it sends a request to the remote database along with your filter criteria.
• The remote database runs the filter function against every document in its store.
• Only documents that pass the filter’s check are sent back to the local device.
• Crucially, this filtering happens on the remote side—so sensitive data for other users never leaves the server for unauthorized devices.

Can it sync only specific user data? Absolutely. #

For your chat app example, here’s how to implement it for Joe and Dan:

1. Structure your remote documents with user identifiers #

First, make sure every document in your remote database includes a clear marker of who owns it. For example:

{
  "_id": "user/secret_informations/Joe",
  "content": "secret information",
  "owner": "Joe"
}

{
  "_id": "user/secret_informations/Dan",
  "content": "secret info again",
  "owner": "Dan"
}

2. Create a filter function on the remote database #

You’ll need to add a design document to your remote CouchDB that defines the filter. For example:

{
  "_id": "_design/chat_filters",
  "filters": {
    "by_owner": "function(doc, req) { return doc.owner === req.query.user; }"
  }
}

This function checks if the document’s owner field matches the user parameter passed during sync.

3. Initiate sync with user-specific parameters #

On Joe’s device, start the sync with his user identifier:

PouchDB.sync('local-chat-db', 'https://your-remote-db-url/chat-db', {
  filter: 'chat_filters/by_owner', // Reference the filter we created
  query_params: { user: 'Joe' } // Pass Joe's ID as the filter parameter
});

Dan’s device will use the same filter but with query_params: { user: 'Dan' }.

Result #

Joe’s local database will only receive documents where owner: "Joe", and Dan’s will only get his own. No cross-user data leakage, and each device only stores the data it needs.

Bonus: Alternative approach using document IDs #

If you prefer to filter based on the document’s _id (like your example path structure), you can adjust the filter function to check the ID instead:

function(doc, req) {
  // Check if the document ID includes the current user's name
  return doc._id.includes(`/${req.query.user}/`);
}

This works just as well—choose the approach that fits your data structure best.

内容的提问来源于stack exchange，提问作者Raold