It's Turbo Time

Leading graph database, Neo4j 1.7 goes GA

Chris Mayer

The culmination of milestone releases, Neo4j 1.7 becomes available to the public with some big upgrades for those aware of its powers

The team behind the powerful NoSQL graph database for
Java, Neo4j has announced that the latest stable version of the
database option is now generally available to the

Codenamed “Bastuträsk Bänk”, Neo4j
represents a quick turnaround cycle for the team, having
released the first milestone back in March. Thoughts turn to the
future as the team are trying to make the graph database much
speedy for enterprises craving a high volume of deployments. To
counter this problem, the team are building towards an ‘Enterprise
Turbo’ package for handling these particularly high-risk scenarios
with more predictable speed.

The first of these speedy improvements out is the
GCR cache
– promising to be 10x faster and 10x more accomodating for
primitives. All in all, the GCR irons out previous rough spots for
those wanting to process larger graphs with several simultaneous
user operations. As long as it’s tuned optimally of course. The
team say this is an ideal option for those dealing with large
cluster deployments.

Another big part of Neo4j 1.7 is the advances made to
Neo4j’s query language, Cypher, striking a balance between clarity
and complexity quite nicely. In response to user feedback, the team
have worked towards providing a complete list of
math functions
 for use with the WHERE and RETURN

Aside from the obligatory tuning under the hood to improve
performance, there’s also 
SSL Support to add remote
access to Neo4j across the public internet and wildcards in
security authorization rules. System properties can override
the configuration as well, to comply with different production

To download Neo4j 1.7,
check out the site, where you’ll also find previous milestones
(refer back to the 1.7.M011.7.M02 and 1.7.M03) which
look at improvements in greater detail. A welcome update for the
premier Java graph database choice. Onward to Neo4j 1.8!

comments powered by Disqus