OrientDB: All content tagged as OrientDB in NoSQL databases and polyglot persistence
I have been trying to avoid graph “intro” slides and presentations.
There are only so many times you can stand to hear “…all the world is a graph…” as though that’s news. To anyone.
This presentation by Luca is different from the usual introduction to graphs presentation.
Original title and link: Why relationships are cool… Relationship in RDBMS vs graph databases ( ©myNoSQL)
Neo Technology’s hiring announcement is clear about their intention:
“[…] you will be resonsible for building, managing, and maintaining a 24x7 NOSQL Databases-as-a-Service operation […]”
Original title and link: Neo Technology Is H… Wait, It’s Building Neo4j-As-A-Service ( ©myNoSQL)
The main page of InfiniteGraph, a graph database commercialized by Objectivity, features an interesting comparison of 7 graph databases (InfiniteGraph, Neo4j, AllegroGraph, Titan, FlockDB, Dex, OrientDB) based on 16 criteria: licensing, source, scalability, graph model, schema model, API, query method, platforms, consistency, concurrency (distributed processing), partitioning, extensibility, visualizing tools, storage back end/persistency, language, backup/restore.
Unfortunately the image is almost unreadable, but Peter Karussell has extracted the data in a GoogleDoc spreadsheet embedded below.
Original title and link: A Comparison of 7 Graph Databases ( ©myNoSQL)
It’s impossible to always have the right answers to all the questions. So this time I’ll have to ask you all: why only some NoSQL databases are present in managed hosting offers?
The first wave of NoSQL managed hosting services brought MongoDB, CouchDB, and some Redis. The second wave brought some more MongoDB, CouchDB, and just a bit more of Redis. It was only the third wave that brought some managed services for graph databases: Neo4j and OrientDB. Plus the first proposal for Cassandra managed hosting.
The first answer that comes to mind when thinking about NoSQL managed services is adoption. If a product is not in wide use then the chances for a company to run a profitable hosting business are very low. But I have the feeling that this is not the only or the complete answer.
Please chime in and share your thoughts.
Original title and link: A Question About NoSQL Managed Hosting ( ©myNoSQL)
In the last few days I’ve read about some new NoSQL hosting solutions:
Cassandra: managed hardware & software hosting:
- Intel Dual Quad-core (8 cpu’s), 16gb of memory, 2tb primary storage + 500gb commitlog drive
- 5 public ip addresses, 1000Mbps private network port.
- Debian, CentOS, RedHat or FreeBSD
- Cassandra setup, configuration and ongoing maintenance (repairs, cleanups, troubleshooting)
- Cassandra upgrades (rolling restart)
- 24x7 real-time monitoring (load, tcp, jmx and cassandra logs)
- Multi-datacenter environment (we’ll spread your cluster across two or three geographic locations, based on your needs)
- 30 days test drive
Cost: $850/monthly per node (5tb bandwidth, includes backups & monitoring)
- Real-time replicated deployment
- JSON over HTTP access
- can offer VPN connections to the cluster
- Cloudeno.de is still in beta
- “one Redis instance free with every Cloudnode account”, but no further details about the characteristicts of the instance
Hosting for NoSQL databases has been available in some form or another for a while, but only for the most popular ones (MongoDB, CouchDB, Redis). Things are changing fast. Neo4j is advertising heavily the Heroku add-on, OrientDB got NuvolaBase, and so on.
This is the market that Amazon is targeting with Amazon RDS, SimpleDB, and DynamoDB: the managed data services and that as part of a bigger strategy. What should be clear is that Amazon is not after NoSQL database companies.
Anyone considering a business in the managed data services market should realize that Amazon will not get into supporting all the NoSQL databases out there. They’d also better take a deep look and learn from what Amazon is offering with SimpleDB and DynamoDB.
Original title and link: Hosted and Managed NoSQL: Cassandra, Redis, OrientDB ( ©myNoSQL)
Such list would be even more useful with the following classification:
Note: A special mention in this category for OrientDB and Terrastore which even if they might not be largely adopted they are still active projects probably counting a couple of production deployments.
Original title and link: 11 Document-Oriented Databases Which Are 8: CouchDB, Jackrabbit, MongoDB, RavenDB ( ©myNoSQL)
A nice intro to Gremlin, the Groovy-based graph traversal language supporting Neo4j, OrientDB, DEX, RDF Sail, TinkerGraph, and ReXster:
Original title and link: An Intro to Gremlin the Graph Traversal Language ( ©myNoSQL)