"couchdb usecase": All content about "couchdb usecase" in NoSQL databases and polyglot persistence
Thursday, 16 December 2010
CouchDB Usecase: Decentralizing Twitter
J.Chris Anderson in an interview over ReadWriteWeb:
Klint Finley: Let’s start at the top: what exactly is Twebz? It’s described as a “decentralized Twitter client.” What exactly does that mean?
J Chris Anderson: The aim is to allow you to interact with Twitter when Twitter is up and you are online. But if Twitter is down for maintenance or you are in the middle of nowhere, you can still tweet. And when you can reach Twitter again, it will go through.
If lots of folks are using it, then they can see each other’s tweets come in even when Twitter is down.
Mostly the goal was to show the way on how to integrate CouchDB with web services and APIs.
A classical example of CouchDB powerful P2P replication capabilities. Dave Winer would probably be its ☞ biggest fan.
Original title and link: CouchDB Usecase: Decentralizing Twitter (NoSQL databases © myNoSQL)
via: http://www.readwriteweb.com/hack/2010/12/j-chris-anderson-interview.php
Wednesday, 11 August 2010
CouchDB, Mobile Devices and The Distributed Web Data
Getting back from two crazy days I’m finding that the big news (at least in the media) is that CouchDB has released an CouchDB SDK for Android. You can read more about how to get it ☞ here.
We already knew that thanks to its friendly protocol and advanced replication features, CouchDB is a solid option when looking for distributed web data, Palm webOS and its db8 usage of CouchDB for replication being a very good example of this CouchDB use case.
CouchDB, Mobile Devices and The Distributed Web Data originally posted on the NoSQL blog: myNoSQL
Wednesday, 16 June 2010
CouchDB Case Study: Web Based IRC
Another CouchDB case study this time from Anologue:
Initial goal: enable any number of people to view a web page that would serve as a sort of chat-room. Generate a link, share it with whomever you’d like to participate in the dialogue, type your name and text to add to the conversation.
I’d speculate that CouchDB was used due to its possibly simplified architecture of the web app and its document-based data model. Definitely not based on some “fake” or just plain wrong reasons.
Adding it to the list of CouchDB case studies.
Tuesday, 8 June 2010
CouchDB and The Distributed Web Data
Michael Hunger (@mesirii) reports on Jan Lehnardt’s talk at Berlin Buzzwords:
Jan also stressed privacy issues and ownership of data, mentioning facebook and the diaspora project. One proposed solution could be to keep more personal data (or at least a safe copy) in a local couchdb instance. (“Every machine should run a webserver anyway - that is one the original ideas of the web.”). If you have those instances on any of your machines then information as:
- contacts
- appointments
- bookmarks and browse history
- even email and IM messages
could be stored as documents in the database and automatically synched (on the database level) to couchdb instances on all the other devices you use.
CouchDB has quite a few features (i.e. a friendly HTTP/REST API, replication and some more) that make it interesting for such distributed web data scenarios.
Friday, 14 May 2010
CouchDB Case Studies
The guys from ☞ Couchio started to publish a series of CouchDB case studies. This is a very good initiative that is on par with myNoSQL intentions. Unfortunately, the three published so far — you can be read them ☞ here — are in my opinion too thin in technical details. Here is a short list of questions that I’d love to hear more about:
Why and how have you got to CouchDB?
Have you had to migrate existing data? How did you do that? Are you still using a relational or other storage solution?
What kind of replication strategy are you using?
Are you sharding you data? If yes, what strategy/solution are you using?
What lessons have you learned while using CouchDB?
If you can help me get these answer I bet it would make these CouchDB case studies even more interesting for the NoSQL community.
Another case study that J.Chris pointed out while I was away is the webOS announcement ☞ mentioned by Ed Finkler @funktron
If you’re into CouchDB and JavaScript, webOS is geting 100% more awesome: #palmdev


Sunday, 10 January 2010
NoSQL Week in Review 6
I am so excited to write this new edition of NoSQL week in review, not only because it marks the sixth installment, but also as it gives me the opportunity to announce a couple of new features I’ve added to MyNoSQL over the last couple of days.
MyNoSQL is currently hosted by Tumblr, which while being a nice blogging platform, is missing quite a few features that I wanted to be able to offer to the NoSQL readers. I have spent some time this weekend looking for solutions and now I’m happy to report that I’ve got everything working.
New right bar widgets
There was no way to provide a list of the recent posts or anything dynamic on the MyNoSQL sidebar. Initially I have considered using a 3rd party solution, but that proved to be even worse than nothing: the widget was taking way too long to load, it was a Flash widget and so not available on mobiles, plus it was completely ugly.
Now, MyNoSQL has these two sidebar widgets that are extremely fast and while not the best looking they at least follow the rest of the UI.

Topics sidebar menu
While offering a nice one-click away navigation option, the NoSQL topics menu on the sidebar was growing too big, So, I have spent some time to reduce its size, while maintaining the functionality and providing a coherent grouping of the options.

A better mobile version
Last, but not least, while visualizing MyNoSQL on your mobile wasn’t too bad, there were things that could be better. Now MyNoSQL has a handheld stylesheet that should provide a better experience for mobile users. I should mention that I have preserved the default styling for the iPhone users as the pinch functionality works pretty well on MyNoSQL. On the other hand, I haven’t been able to crack BlackBerry’s rendering engine secret and it is still ignoring completely the changes I have made (nb any help to address this issue is highly appreciated).
Unfortunately I don’t have any screenshots to show, but hopefully by the end of next week I’ll receive the new mobile phone and I’ll be able to show it to you. Anyway, you can try it right now!
I really hope you’ll find these useful and if you have suggestions please do let me know. And now to our usual weekly NoSQL topics.
What’s Hot in the NoSQL World
- On Why I Think These Pro MongoDB Arguments Are Not Unique…
- MongoDB Usecases
- NoSQL Twitter Applications
- Notes on Distributed Programming and CAP
- Some Shallow & Superficial Reasons for Picking MongoDB for your [web]app
It is interesting to note, how 3 top articles this last week have been focusing on MongoDB features and applications. Unfortunately, two articles I’ve strongly encourage you to read: Redis Virtual Memory and A Step-by-Step Intro to HBase with Ruby haven’t made it to the what’s hot in the NoSQL world.
New NoSQL Releases
It looks like the NoSQL teams have worked hard to make releases before the year ended. Last week we’ve seen at least 3 releases: MongoDB 1.2.1, Terrastore and Neo4j 1.0-b11.
This week, I have only noted a minor release of Terrastore 0.3.1 and the blocking implementation of Redis VM. In case I have missed anything please do let me know immediately.
NoSQL Week in Review
- MongoDB Usecases
(Tags: ) - Neo4j Node Indexing
(Tags: ) - A Step-by-Step Intro to HBase with Ruby
(Tags: ) - Hadoop Tutorial Part 2: Getting Started with Partitioning
(Tags: ) - Tokyo Cabinet and CouchDB as Mnesia backends
(Tags: ) - The guys over ☞ the changelog have published an interview with…
(Tags: ) - Notes on Distributed Programming and CAP
(Tags: ) - NoSQL Twitter Applications
(Tags: ) - On Why I Think These Pro MongoDB Arguments Are Not Unique…
(Tags: ) - Fun with the CouchDB _changes feed and RabbitMQ
(Tags: ) - Redis Virtual Memory
(Tags: ) - Some Shallow & Superficial Reasons for Picking MongoDB for your [web]app
(Tags: ) - Not Everyone Wants to Be MapReduce Friendly
(Tags: ) - FOSDEM NoSQL Devroom Agenda Announced
(Tags: ) - Basic Benchmark: CouchDB vs MongoDB vs MySQL
(Tags: )