rawjeev's randoms

Text

OrientDB 1.0…1.1

I fell in love with #OrientDB first time I came across it.

What I like about OrientDB are the following:

A cool, high performance, #nosql DB.
You can use it in the flavor you prefer: Document DB, Object DB, Graph DB.
Use it Embedded, as a Server or Clustered.
A NOSQL DB that supports SQL (like) queries.
A liberal Apache2 license.

While 1.0 (around the corner) looks like an important milestone to reach, 1.1 that’s coming seems more exiting.

A list of some interesting features to come in version 1.1:

Data compression at storage level - Storage efficiency
Data repair tool - Will give some confidence should something go wrong in a production db
Lucene integration - Should improve performance
SSL support for binary & HTTP connections - Security during transmission is important.
Time Machine (revisions/versioning) - Can address some interesting use cases
Support for Stored procedures - We have applications with lot of things done as stored procedures (though I don’t like it), I expect support for stored procedures should make it easy to migrate to OrientDB.
And others: Views, Sub queries, VFS, …

(Source: code.google.com)

Tags: nosql orientdb tech

June 24, 2011

0 comments

6 notes

Text

OrientDB

What I Like:

A NoSQL Document Database that supports SQL,
A friendly Apache 2.0 license.
Supports Schema-less & Schema-full or Mixed modes
Distributed & Transactional

I’d have liked it better if:

There was SPARQL support.

See: http://www.orientechnologies.com/

Others I’m looking at:

Tags: nosql orientdb tech

September 19, 2010

0 comments

Link

How RDF Databases Differ from Other NoSQL Solutions - The Datagraph Blog

(via: late2theparty:)

This is a VERY (very) well written introduction to RDF and it’s relevance to the NoSQL movement. The article stresses that RDF is, currently (as of April 2010), the only NoSQL solution that is standardised upon, which includes the ability to query it via an SQL-like query interface, such as SPARQL.

If you like to see a small N-Triples (an RDF export format) and SPARQL sample, see this stackoverflow post. Given [from stackoverflow]:

1 <- 2 -> 3
3 <- 4 -> 5

these are already subject predicate object form so just slap some URI notation on it, load it in the triple store and query at-will via SPARQL. Here it is in NT (N-Triples) format:

<http://mycompany.com#1> <http://mycompany.com#2> <http://mycompany.com#3> .
<http://mycompany.com#3> <http://mycompany.com#4> <http://mycompany.com#5> .

Now query for all nodes two hops from node 1:

SELECT ?node
WHERE {
    <http://mycompany.com#1> ?p1 ?o1 .
    ?o1 ?p2 ?node .
}

This would of course yield <http://mycompany.com#5>.

What the example query is doing is identifying data associated with the specified input RDF ‘node’, and then requesting an RDF node adjacent to this node within another RDF triple/axis (forgive my terminology).

A notable RDF ‘store’ mentioned in the [comments of] the post above is Bigdata store, which is hailed as scaling very well (it is free and open-source).

Java RDF access libraries include Jena and Sesame, which intern should be accessible via JVM-compatible languages such as Scala.

Tags: tech nosql rdf semanticweb

August 06, 2010

0 comments

Link

Is the Relational Database Doomed?

techpost:

Recently, a lot of new non-relational databases have cropped up both inside and outside the cloud. One key message this sends is, “if you want vast, on-demand scalability, you need a non-relational database”.

Read it…

and then you must also read The dark side of NoSql

Tags: tech nosql

February 10, 2010

0 comments