OrientDB 1.5 has been released, fix a bunch of issue and bring the following new feature and enhancement:
All the issues: https://github.com/orientechnologies/orientdb/issues?milestone=5&page=1&state=closed
- New PLOCAL (Paginated Local) storage engine. In comparison with LOCAL it’s more durable (no usage of MMAP) and supports better concurrency on parallel transactions. To migrate your database to PLOCAL follow this guide: migrate-from-local-storage-engine-to-plocal
- New Hash Index type with better performance on lookups. It does not support ranges
- New “transactional” SQL command to execute commands inside a transaction. This is useful for “create edge” SQL command to avoid the graph get corrupted
- Import now migrates RIDs allowing to import databases in a different one from the original
- “Breadth first” strategy added on traversing (Java and SQL APIs)
- Server can limit maximum live connections (to prevent DOS)
- Fetch plan support in SQL statements and in binary protocol for synchronous commands too
Upgrade note: https://github.com/orientechnologies/orientdb/wiki/Upgrade
Download link: https://github.com/orientechnologies/orientdb/releases/download/1.5/orientdb-graphed-1.5.0.zip
Congratulations to the OrientDB team: release 1.0 is finally out !
List of major changes
- new Multi-Master Replication architecture
- new Object Database interface that use run-time enhancement. Now handles lazy loading, it’s lighter and faster than before
- new OTraverse class to traverse graphs via Java API using a stack-free approach
- Data segments: added support for multiple ones and create/drop commands
- new ODocument.undo() to revert local changes
- new Server Side Scripting support
- Query: new context variables
- Console: new check database command
- Studio: improved Graph management
- Improved OSGi support
- Fixed more than 40 bugs
“GraphDB in PHP: time for the serious stuff” is a great presentation made by Alessandro Nadalin(www.odino.org) during the national PHP conference aka PHPCon Poland 2011.
It introduces an ecosystem of graph databases, which are storage system using graphs as their primary data structures and persisting PHP objects to the DB.
And also available on slideshare:
You’re currently looking for a GraphDB, quick tour of the existing solution:
- Neo4j is an embedded, disk-based, fully transactional Java persistence engine that stores data structured in graphs rather than in tables.
- DEX is a high performance library to manage very large graphs or networks
- HyperGraphDB: a general purpose, extensible, portable, distributed, embeddable, open-source data storage mechanism.
- InfoGrid: an Internet Graph Database with a many additional software components that make the development of REST-ful web applications on a graph foundation easy.
- Vertexdb: a high performance graph database server that supports automatic garbage collection.
- AllegroGraph RDFStore: a modern, high-performance, persistent RDF graph database.
- Filament: a graph persistence framework and associated toolkits based on a navigational query style.
- OrientDB: a document and graph capable with strong security profiling system