nawroth

Develop a Graph

There are Three APIs…​

Neo4j has a trio of programming interfaces, focused on different kinds of interaction.

• Work with the Cypher query language over HTTP.

• Discover raw graph primitives over REST.

nawroth

Orienteering Gist

This is the Orienteering Dataset based on the blog.neo4j.org post.

It’s a simple, three-leg training course in an Antwerp park. Setting this up as a graph in neo4j was easy enough:

nawroth

Movie Database

Our example graph consists of movies with title and year and actors with a name. Actors have ACTS_IN relationships to movies, which represents the role they played. This relationship also has a role attribute.

We’ll go with three movies and three actors:

nawroth

Social Movie Database

Our example graph consists of movies with title and year and actors with a name. Actors have ACTS_IN relationships to movies, which represents the role they played. This relationship also has a role attribute.

So far, we queried the movie data; now let’s update the graph

nawroth

Finding Paths

Our example graph consists of movies with title and year and actors with a name. Actors have ACTS_IN relationships to movies, which represents the role they played. This relationship also has a role attribute.

We queried and updated the data so far, now let’s find interesting constellations, a.k.a. paths.

nawroth

The case for CASE

This is how you might model Premier League managers tenures at different clubs in Neo4j:

The date modeling is based on an approach described in more detail in Return partly shared path ranges.

nawroth

this is the title

MATCH (n) RETURN n

nawroth

Using labels

Labels is a convenient way to group nodes together. They are used to enhance queries, define constraints and indexes.

The following will give an example of how to use labels. Let’s start out adding a constraint — in this case we decided that all Movie nodes should have a unique title.

nawroth

Testing document attributes

{my-attribute}

{someattribute}

nawroth

Neo4j Documentation

The Neo4j Manual is versioned and released together with the product. An overview of parts of the documentation workflow is found in the manual itself, in the chapter Writing Neo4j Documentation. We use several different approaches to verify our documentation by tests running in CI when the product is built. Testing as much as possible of examples especially makes sense, as we also provide ways to interactively play with Neo4j, see for example Create nodes and relationships.

The documentation toolchain also makes sure that all cross references have valid targets.

The core tools for our documentation are AsciiDoc and DocBook.