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

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

A Human-Readable Jackrabbit Persistence Manager Prototype for Orientdb

Jackrabbit still has a very special place in my heart. I’ve fought it many times, sometimes losing, most of the time winning. But for over 7 years now, it is still the main storage engine serving the content of InfoQ. So this OrientDB engine for Jackrabbit by Thomas Kratz caught my attention:

This has some limitations, as jackrabbit will still access only one node at a time, being able to traverse the graph at the storage level is simply not intended by the whole api. But it works, it’s readable, can be modified at the db level easily.

Original title and link: A Human-Readable Jackrabbit Persistence Manager Prototype for Orientdb (NoSQL database©myNoSQL)

via: http://thomaskratz.blogspot.de/2013/01/a-human-readable-jackrabbit-persistence.html


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)

via: http://codex.grimoire.ca/2011/11/25/ldap-101-its-a-database-stupid/


Comparing Jackrabbit (JCR) and CouchDB

During Berlin Buzzwords NoSQL event, I was asked to compare Jackrabbit and CouchDB, so I hope this will offer a more structured and complete comparison.

via: http://bergie.iki.fi/blog/what_is_a_content_repository/