3 ms·

Another interesting approach is: - CouchDB - PouchDB: https://github.com/daleharvey/pouchdb https://github.com/daleharvey/pouchdb - Backbone PouchDB Adapter:

Another interesting approach is: - CouchDB - PouchDB: https://github.com/daleharvey/pouchdb https://github.com/daleharvey/pouchdb - Backbone PouchDB Adapter: https://github.com/jo/backbone-pouchdb https://github.com/jo/backbone-pouchdb But the Map-Reduce paradigm didn't seem to fit well onto our data model.

cloudmike 14y ago
Our goal on the client-side (compared to CouchDB) was simpler, more lightweight libraries that work well with existing tools that developers already use, like Core Data on iOS and sqlite/ContentProviders on Android. Whereas CouchDB does master-master replication among instances of itself, Simperium can accomplish something similar with any database: e.g. sqlite on iOS, to MongoDB in our backend, and to whatever database you use in your own backend.
- akrymski 14y ago
  Just strange that you don't support offline for web apps, only iOS & Android, even though web apps can use websql. That's probably cause you're used to writing native iOS apps, but we're attempting a web app that works via phonegap across all devices from one source code base. So for us storing all the data in Backbone collections isn't an option - models add too much memory overhead, versus native JSON objects. As I understand multiple collections update independently of each other? How do you deal with relational data in that case?
  - cloudmike 14y ago
    Consistent browser support for storage (besides localStorage) is still quite frustrating. It's improving though and we're on it. You can model relational data in Backbone quite effectively, or use another library (or your own). For example: https://github.com/PaulUithol/Backbone-relational/ https://github.com/PaulUithol/Backbone-relational/
daleharvey 14y ago
The map reduce paradigm isnt particularly core to PouchDB, it mostly in there for completion, I expect a fairly large amount of more powerful and easier to use querying mechanisms on top of PouchDB The data syncing is by far the priority

cloudmike 14y ago

Our goal on the client-side (compared to CouchDB) was simpler, more lightweight libraries that work well with existing tools that developers already use, like Core Data on iOS and sqlite/ContentProviders on Android. Whereas CouchDB does master-master replication among instances of itself, Simperium can accomplish something similar with any database: e.g. sqlite on iOS, to MongoDB in our backend, and to whatever database you use in your own backend.

akrymski 14y ago
Just strange that you don't support offline for web apps, only iOS & Android, even though web apps can use websql. That's probably cause you're used to writing native iOS apps, but we're attempting a web app that works via phonegap across all devices from one source code base. So for us storing all the data in Backbone collections isn't an option - models add too much memory overhead, versus native JSON objects. As I understand multiple collections update independently of each other? How do you deal with relational data in that case?
- cloudmike 14y ago
  Consistent browser support for storage (besides localStorage) is still quite frustrating. It's improving though and we're on it. You can model relational data in Backbone quite effectively, or use another library (or your own). For example: https://github.com/PaulUithol/Backbone-relational/ https://github.com/PaulUithol/Backbone-relational/

daleharvey 14y ago

The map reduce paradigm isnt particularly core to PouchDB, it mostly in there for completion, I expect a fairly large amount of more powerful and easier to use querying mechanisms on top of PouchDB The data syncing is by far the priority