Featured Post

This Week in Neo4j – West Africa Leaks, GQL Online Meetup, Geospatial Deep Dive, CoinMarketCap Analysis

Welcome to this week in Neo4j where we round up what’s been happening in the world of graph databases in the last 7 days. This week we have West Africa Leaks from the ICIJ, an online meetup about the GQL proposal, a Deep Drive into the Geospatial Data Type, analysis of CoinMarketCap... read more


Learn about the Neo4j 3.4 GA release in less than 8 minutes, including scalability and performance improvements

Neo4j 3.4 Release Highlights in Less Than 8 Minutes [Video]

Hi everyone, My name is Ryan Boyd, and I'm on the Developer Relations team here at Neo4j. I want to talk with you today about our latest release Neo4j 3.4. Overview In Neo4j 3.4 we've made improvements across the entire graph database system, from scalability and performance, to... read more


This Week in Neo4j – 3.4 Released, Neo4j on Google Cloud Launcher, GQL Proposal, DateTime Deep Dive

Welcome to this week in Neo4j where we round up what’s been happening in the world of graph databases in the last 7 days. This week we have the release of Neo4j 3.4 and Neo4j is now available on Google Cloud Launcher. We also have the GQL proposal, a deep dive into the new DateTime... read more



Learn what's new in Neo4j 3.4, including Multi-Clustering, Cypher performance and new data types

Neo4j Graph Database 3.4 GA Release: Everything You Need to Know

Author's note: What a hectic week in the world of Neo4j! In addition to finalizing the delivery of Neo4j 3.4, we simultaneously built the GQL Manifesto, a call to support a common, unified Graph Query Language. Thank you to the graph community for your strong vote of support! If you have not... read more


Discover why it's time for a single property graph query language (GQL), just like SQL for RDBMS

It’s Time for a Single Property Graph Query Language [Vote Now]

The time has come to create a single, unified property graph query language. Different languages for different products help no one. We’ve heard from the graph community that a common query language would be powerful: more developers with transferable expertise; portable queries; solutions... read more