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



Can Anyone Use the Name Hadoop?

The short and the only answer that makes sense is NO.

If you don’t immediately agree or understand why, there’s a page on the Hadoop wiki: Defining Hadoop that can help everyone wanting to use Hadoop in their product names. I strongly encourage you to read it carefully.

Just to get a gist of it:

“The key point is that the only products that may be called Apache Hadoop or Hadoop are the official releases by the Apache Hadoop project as managed by that Project Management Committee (PMC). It’s also important to remember that HADOOP is a registered trademark of the Apache Software Foundation.”

“All products which include the official Apache Hadoop artifacts, or included artifacts that are somehow on the source code used to generate these artifacts are derivative works. […] Derivative works may choose to declare that they are Powered by Apache™ Hadoop®.”

“The key point is this: the Apache Hadoop codebase defines what Apache Hadoop is, so only that codebase can not only assert that it is 100% compatible with Apache Hadoop, but back it up implicitly: Apache Hadoop is compatible with Apache Hadoop, because it is Apache Hadoop.”

Before using the Hadoop name, make sure you spend some time on this page and especially the Examples section.

Case closed.

Original title and link: Can Anyone Use the Name Hadoop? (NoSQL database©myNoSQL)