@pubkey Great, now we understand each other.
So basically rxdb puts more of the workload on the server, because the server now has to maintain a view for every document type and handle more http requests. In return, the client has multiple database instances to work with, which can have the advantages you mentioned.
Have there been any benchmarks or comparisons between these two approaches and how well they scale?
It seems likely that the rxdb approach requires a more powerful server to serve the same number of clients but it would be interesting to know how much more powerful. Cloud bills are expensive, so some quantitative approximation of the difference would be really interesting to know.
Also a relevant question: For which kind of use cases and at what workloads does the rxdb approach (multiple database instances on the client side) start to pay off?
Has there been any work in that direction? @jaredly Could that be an interesting aspect for your review?
That was one of the main reasons why I also added the GraphQL replicatoin
So if I write a query like
sort({a: ‘desc’, b: ‘asc’ }) the asc of b is ignored.After reading pubkey/rxdb#1972, I tried using
.sort([{ a: ‘desc’ }, { b: ‘asc’ }]), which results in an error.I made a codesandbox demo here. Is there something I am missing or is this a bug?
sort: ["-a", "b"]
Hm I was referring to this documentation: https://pouchdb.com/api.html#query_index (search for ’desc’).
However, it look like it’s indeed an unresolved PouchDB Bug: pouchdb/pouchdb#7863
@/all
I just released the new major version 9.0.0.
Upgrade now!
open_revs: true throwing error from pouchDb. Shouldn't this be open_revs: 'all'or my pouchDb has wrong config.
export function getDocFromPouchOrNull(
collection: RxCollection,
id: string
) {
return collection.pouch.get(id, {
open_revs: true
})
.then(docData => {
return docData;
})
.catch(() => null);
}
https://deepstream.slack.com/
https://deepstream.io/
@pubkey thank you for your reply,
for the offline storage, I made a quick search and it seems implemented https://github.com/deepstreamIO/deepstream.io-client-js/search?q=offline&type=Code
For replication, it seems they could replicate to many databases (postgres, mongos, rethinkdb) using connectors:
https://github.com/deepstreamIO/deepstream.io-storage-elasticsearch, https://github.com/deepstreamIO/deepstream.io-storage-mongodb, https://github.com/deepstreamIO/deepstream.io-storage-rethinkdb, https://github.com/deepstreamIO/deepstream.io-storage-postgres
@/all