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



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

Presentation: An Introduction to FluidDB

We briefly covered FluidDB in the past when I mis-named it the Wikipedia of databases. The presentation embedded below clarifies a bit more the following questions:

  • what is FluidDB: a platform for the web of things, each represented by an openly writable “social” object
  • why FluidDB: most of the information nowadays lives inside walled gardens, so its difficult to make real use of it. I especially enjoyed this slide explaining the problem with closed information:
    Issue with walled garden information
  • how to use FluidDB: all applications use the same FluidDB database through a RESTful API

NoSQL Ecosystem News & Links 2010-03-22

  1. A short version of NoSQL week in review, after losing the original post.
  2. Nicholas J. Radcliffe: ☞ Alice in FluidDB. The power of tagging.
  3. ☞ A graph theory book by David Joyner, Minh Van Nguyen, and Nathann. Helpful for everyone interested in graph databases.
  4. Jeff Darcy: ☞ Riak and Cassandra. It wasn’t long until someone jumped at/corrected Riak’s comparisons with Cassandra, MongoDB and Neo4j. And now there is a comment on the Basho blog: ☞ The Craft Brewers of NoSQL

    I think the market is still too young and small to see real attacks between the players. But once the market will grow in size, we will unfortunately start seeing some of these. Hopefully, myNoSQL readers will know how to make the difference!

    And the conversation ☞ ends with beers!

  5. Till Klampaeckel: ☞ Redis on Ubuntu (9.04)
  6. Daniel Wertheim: ☞ Simple-MongoDB – Support for Regex and custom Id’s.
    Not sure it’s just an impression but there seems to be a lot of activity on the MongoDB and C# space. Luckily, we have this covered for you:
  7. Salvatore Sanfilippo: ☞ Redis weekly update #2 - Real world hashes, refactoring, and fixes

FluidDB Proposal is Brilliant, But…

It looks like initially I have misunderstood what FluidDB is by calling it a “Wikipedia of databases“. A ☞ post on the FluidDB blog has clarified it for me, so I came up with another definition: “a persistent post-it database service in the cloud”.

While reading the blog post — and leaving aside the fact that as any NoSQL solution it came up with a Twitter-related application — I have found myself getting really excited at the idea. But then, I have realized that:

  1. there must be someone creating such an application
  2. the associative pattern suggested by FluidDB, while being nice will have to be extremely carefully implemented in the app
  3. (this is the most interesting from our NoSQL perspective) there doesn’t seem to be anything unique in FluidDB that would make such a usecase non-applicable to any other NoSQL solution.

Let me clarify it a bit. Basically the article introduces the idea of being able to associate metadata with any kind of information and keep this metadata under clear access rules. In my opinion this is just a simple associative relationship (think key-value stores) that could be implemented using any of the NoSQL solutions we are covering here. Moreover, I tend to think that document databases, like CouchDB, MongoDB, Riak or Terrastore would offer natively a lot of flexibility on the metadata “(un)structure”

Am I wrong?

Taking a look at a fascinating FluidDB usecase that seems to be easily supported by any NoSQL solution. Or not?

Putting metadata onto tweets with FluidDB

I haven’t heard much about ☞ FluidDB before, so I was curious to read this use-case built around Twitter. I have to confess that I’m still not sure I understand what FluidDB is and what are its goals, but after skimming a bit through the website, I left with the feeling that FluidDB is a sort of Wikipedia of databases.

FluidDB Resources

In case you come up with a better idea of what FluidDB is do share it with us!