once bitten

words and things from Edd Dumbill 
Filed under

nosql

 

CouchDB on Android: why you should care

The kicker though is that CouchDB already solves the data sync problem for you. Users expect to be able to take their data wherever they go and sometimes, if not often, that means they can’t access the cloud and need a local copy. CouchDB on Android lets you build web-apps or native apps that take full advantage of CouchDB’s built-in, reliable peer-to-peer sync facilities.

At first glance, having the NoSQL database CouchDB available on Android seems strange. Why would you need such a thing?

The answer is device-to-cloud synchronization. This is something CouchDB will provide you, without you needing to write sync logic yourself, so you can write client apps that stay in sync with web services.

This is how the Ubuntu Linux desktop maintains synchronization between your Evolution address book and their cloud service.

Watching eagerly!

Loading mentions Retweet

Filed under  //   android   cloud   couchdb   mobile   nosql   sync  

Comments [2]

NorthScale Membase server is a memcached layer over a relational DB

NorthScale Membase Server is a high-performance, distributed key-value database which builds on the NorthScale Memcached Server foundation. Directly compatible with memcached APIs and client libraries, NorthScale Membase Server provides a place to store web application data far more efficiently and cost effectively than it can be stored in a relational database. While memcached reduces the number of reads an application must do from the database, data is still ultimately stored in a relational database. Using NorthScale Membase Server an organization can identify and gradually “drain” data from a relational system to Membase, enjoying the simple, fast and infinite properties of memcached across both reads and writes, while slashing data management costs.

via Chris Wensel.

Loading mentions Retweet

Filed under  //   memcache   nosql  

Comments [0]

Digg are Looking to the future with Cassandra

The fundamental problem is endemic to the relational database mindset, which places the burden of computation on reads rather than writes. This is completely wrong for large-scale web applications, where response time is critical

Watching with interest.

Loading mentions Retweet

Filed under  //   cassandra   databases   digg   nosql  

Comments [0]