Earlier quoted context omitted.
Other than Couch/Pouch, are there any other projects providing solutions to this problem? The one thing I dislike about couchdb is the default "user-per-db" model. I'm interested in solutions that allow a traditional relational db instead of a key-value store. Seems like with indexeddb on the client, and postgres on the server, you could probably keep a segment synced.
I haven't found one and I really wonder if everybody rolls their own sync solution. > The one thing I dislike about couchdb is the default "user-per-db" model. Why exactly? I think the overhead of the DBs is rather small. It's not like having a MySQL DB for every user ;) Also, you can achieve something like "global data" as well: Either replicate from users' DBs to a shared DB or maybe make some kind of "system" user…
Let's say you are making a CRM with couch/pouch. Let's say that you have permissions to see a Customer record, but it is shared across your company. How do you sync that? It's not owned by a user, it's owned by the company. What happens if permissions change?