ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

mobiles: All content tagged as mobiles in NoSQL databases and polyglot persistence

Build Your Mobile Back-End with MongoDB

Will Shulman, from MongoLab, talking about mobile app development using MongoDB for the back-end.

And the slides:

Original title and link: Build Your Mobile Back-End with MongoDB (NoSQL databases © myNoSQL)


CouchDB and the CouchOne Mobile Platform Podcast

A conversation with CouchOne’s Aaron Miller[1] and Nitin Borwankar[2] about the CouchDB application environment and CouchOne efforts to port it to Android and more generally to mobile platforms. The mp3 ☞ hosted by IBM developerWorks website can be downloaded from ☞ here (mp3).


  1. Aaron Miller: CouchOne engineer  ()
  2. Nitin Borwankar: CouchOne VP of Business Development  ()

Original title and link: CouchDB and the CouchOne Mobile Platform Podcast (NoSQL databases © myNoSQL)


CouchDB: A Great Option for Mobile Computing

Even if Krishnan Subramanian’s title is CouchDB and SaaS, he got the part about CouchDB and mobile development right:

  • CouchDB is also an HTTP server. This lets browsers talk directly to CouchDB. This makes mobile app development easy with CouchDB
  • One can easily replicate the whole database, application logic and the data to the mobile device. It will just work out of the box without any extra coding. Just a few javascript tweaks and CSS tweaks will make it work on the mobile device offering the same user experience
  • CouchDB can run on multiple devices and can sync with each other and the cloud whenever there is an internet connection. This offline use and syncing is one of the unique features of CouchDB. CouchDB uses a built in conflict management system and it easily helps solve any conflict that may occur in collaborative SaaS applications
  • The file format of CouchDB is a tail-end format. All changes are added to the end of the database file, thereby, ensuring that database is never in an inconsistent state. For example, if a mobile app gets killed for any reason, you are safe
  • Memory footprint is very low. In a very active state, the database consumes only 7 MB of RAM and less during other times. This makes CouchDB very suitable for mobile devices which usually carry lower memory
  • Geospatial Index – very useful in the case of location aware apps

As covered in the past, I can confirm the mobile is an important aspect of CouchDB adoption strategy.

Original title and link: CouchDB: A Great Option for Mobile Computing (NoSQL databases © myNoSQL)

via: http://www.cloudave.com/7011/saas-startups-should-check-out-couchdb-first/


Redis in Production: Bump Technologies

According to Jamie Turner (@jamwt) Bump Technologies, producers of the mobile app bump that enables data exchanges through bumping phones together, is using Redis in production:

@antirez Who is using Redis? Bump Technologies is using redis in production ( http://bu.mp )

If anyone has details, I’d love to hear more about this Redis case study.

Original title and link: Redis in Production: Bump Technologies (NoSQL databases © myNoSQL)


CouchDB for Android. iPhone Next?

CouchDB got quite some press with the announcement of CouchOne Mobile[1]. In the light of the changes in Apple policy[2], I am wondering if the iDevices (iPad, iPhone, iPod Touch) are next.

Anyway, I think there are additional ingredients to be added to the mix to make CouchOne Mobile see some traction:

  1. becoming rock solid. It is in direct competition with tools like SQLite which are rock solid
  2. there will be tons of applications that would require synchronization with remote servers. Remember, CouchDB strongest point is replication.
  3. there will be some good and cheap CouchDB hosting providers. When you sell $1.99 apps, you’ll not pay tons of dollars for hosting.

Update: while this comment from ☞ Damien Katz about CounchDB coming to iOS is pre Apple policy change, it is a good sign that Couchio CouchOne is trying to get it working as soon as possible:

Aaron Miller and I got Erlang booting up on iOS. CouchDB coming to an Apple device near you.

Update: Six month later iOS Mobile Couchbase is here.


  1. Just perform a Google search after ☞ couchone mobile and pick one of the results (they are all the same) to read the announcement.  ()
  2. John Gruber has a nice coverage of the changes ☞ here  ()

Original title and link for this post: CouchDB for Android. iPhone Next? (published on the NoSQL blog: myNoSQL)


NoSQL CouchDB founder turns to phone and cloud services

Gavin Clarke (The Register):

NoSQL start-up CouchIO is targeting mobile and clouds after just a year of trying to monetize the company’s CouchDB document store.

[…]

Rather than to replace SQLite, Katz believes that CouchDB has a future by being used in addition to SQLite — primarily on document-centric apps such as email, calendaring, scheduling, contacts, CRM, time sheets, and inventory. “That’s where Couch really shines,” Katz said.

Back to origins?[1]


  1. Before creating CouchDB, Damien Katz has been working on Lotus Notes.  ()

Original title and link for this post: NoSQL CouchDB founder turns to phone and cloud services (published on the NoSQL blog: myNoSQL)

via: http://www.theregister.co.uk/2010/09/08/couchone_couchdb_nosql_new_name/


NoSQL Ecosystem News & Links 2010-05-20

  • Running CouchDB on the Android powered Motorola Droid
  • ☞ Riakfuse: Filesystem backed by Riak. Cool!