Graph database: All content tagged as Graph database in NoSQL databases and polyglot persistence
Over the weekend I’ve watched two interviews with people working on Neo4j. Each of them covers it from a different angle: Ian Robison’s interview is the technical one, while Emil Eifrem is giving more of the vision, business, enterprise interview. Pick the type of topic you like and watch it. Both are great though.
If you like going back in time, I’ve found a couple of old presentations from and interviews with Emil Eifrem:
Original title and link: Neo4j Interviews: The Vision, the Business and Enterprise Talk, and the Tech ( ©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.
This article demonstrated how to install Neo4j and the basic idea of how to integrate it with a Ruby/Rails application using the different solutions available. Even though the examples given here barely scratched the surface of Neo4j, it should hopefully give you enough knowledge and curiosity to start integrating it on your own projects.
Original title and link: Using Neo4j Graph Database With Ruby ( ©myNoSQL)