The release of Neo4j 2.0 comes with a brand new browser and Model

Http://www.infoq.com/cn/news/2014/01/neo4j-2

Recently, Neo Technology released Neo4j 2.0 GA with a brand new graph browser, node label, an optional mode, and improved Cypher.

The most noteworthy improvement of Neo4j 2.0 is the brand new browser UI, which allows users to view and edit data through graphs or tables. The following is an example of the movie database. It shows the relationship between an actor and some of the films he participates in (Gray) and other actors (red:

Nodes can now have tags. You can use tags to mark nodes as belonging to a group. A node can have multiple labels.

Neo4j 2.0 also adds support for the mode, but this is optional and seems a bit like a regression to a relational database. The add mode is mainly used to include metadata and improve query execution.

The Cypher query language has also been improved, mainly through optional match and MERGE clauses, the literal node mode, and the ability to return the literal map and collection.

We have the honor to interview Michael Hunger, the leader of Spring Integration and the developer of Neo Technology, to learn about the compatibility issues of Neo4j 2.0, the use of models, and the future roadmap.

InfoQ: What are the compatibility issues between Neo4j 2.0 and earlier versions?

MH:Neo4j 2.0 has made breakthroughs, enhancing the data model, adding the label Concept and optional mode information.

In addition, the query language Cypher has undergone considerable innovations since 1.9. For Embedded APIs, read transactions have become necessary. In addition, this version also deletes a lot of content that was previously marked as not recommended.

For details, see:

Http://www.neo4j.org/release-notes#2.0.0

Http://docs.neo4j.org/chunked/2.0.0/deployment-upgrading.html#deployment-upgrading-two-zero

InfoQ: How does the newly introduced Model accelerate the query speed?

MH:The optional mode information (TAGS) supports indexes and unique constraints. They are automatically used in queries to convert filtering conditions to index searches. In addition, using tags as a part of the query allows the database to scan only the entire database subset when searching for non-index information. Third, the tag information is embedded in the node record. Therefore, it is very simple to test the tag information of an existing node, and you do not need to look for attributes or links further.

InfoQ: What if the database changes? Do I still need to manually update the mode?

HM:When the data changes, the index and constraint information will be synchronized with the data.

For example, to add a new tag, you need to provide a new index/constraint definition. However, existing data enhanced by the new tag is automatically indexed.

InfoQ: What is the future roadmap of Neo4j?

MH:

• Continuously improve user experience
• Performance (read, write, query language)
• Added (artificial) Restrictions on nodes and relationships
• Better import/export functions
• BI/Integration
• Operational improvements
• Some big data/graph computing
• Installation experience
• Improved remote/driver

View Original English text:Neo4j 2.0 Comes with a New Browser and a Schema