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



LDAP: It's a (Non-Relational) Database, Stupid

The topic of LDAP shows up from time to time when speaking about non-relational databases. While I do encourage you to read the whole post, just check this summary:

LDAP is a protocol and a data model for providing access to a hierarchal (tree-shaped) database. The database itself is normally referred to as a “directory” (hence the name), a bit of nomenclature inherited from its predecessor, X.500, populated with objects that are bundles of attributes. LDAP supports direct lookup of an object by name, searches through subtrees or through the whole directory for objects matching a sophisticated pattern language, atomic updates to part of or all of individual objects, and network federation.

How many of these features are fundamental parts of the what we call today NoSQL databases?

But LDAP, like the other hierarchical storage implementing the Java Content Repository spec[1], didn’t fly too high. What NoSQL can learn from LDAP history discusses some possible causes of LDAP’s “failure”.

  1. Disclaimer: years ago I’ve been a big proponent of the JCR and one of the most interesting systems I’ve built is using a JCR implementation (but also a relational database and soon another NoSQL database).  

Original title and link: LDAP: It’s a (Non-Relational) Database, Stupid (NoSQL database©myNoSQL)