As we’ve been deploying and testing the Neo4j 3.0 Milestone releases on GraphGrid we’ve been excited for some of the shiny new features and also taking note of the operational differences that we’ll need account for in preparation for supporting Neo4j 3.0.
Neo4j is the most popular option in today’s graph database space with its native
Neo4j 3.0 Feature Highlights
Some of the features in Neo4j 3.0 that we’re enjoying are the following in no particular order:
The upgrade to Lucene 5 comes with many performance improvements and other improvements made to the Lucene library since version 3 that was previously being used by Neo4j. Lucene is a high-performance, full-featured text search engine library written entirely in Java that Neo4j uses for some indexing operations so this brings some nice improvements to the indexing management and performance within Neo4j.
The introduction of a uniformed language driver, called Bolt, that greatly improves performance and capability of the language drivers that communicate with the Neo4j
graph database completely remotely.
The introduction of a uniformed language driver, called Bolt, that greatly improves performance and capability of the language drivers that communicate with the Neo4j
graph database completely remotely.
Complex graph update operations using MERGE are probably our most used Cypher operations for loading data into Neo4j and keeping it updated constantly during various ETL processes when integrating Neo4j with existing data sources. This makes the Cypher improvements to the cost-based planner to supper update
No comments:
Post a Comment