Spring Data Graph is an integration library for the open source graph database Neo4j and has been around for over a year, evolving from its infancy as brainchild of Rod Johnson and Emil Eifrem. It supports transparent AspectJ based POJO to Graph Mapping, a Neo4jTemplate API and extensive support for Spring Data Repositories. It can work with an embedded graph database or with the standalone Neo4j Server.
The session starts with a short introduction to graph databases. Following that, the different approaches using Spring Data Graph are explored in the Cineasts.net web-app, a social movie database which is also the application of the tutorial in the Spring Data Graph Guidebook. The session will also cover creating a green-field project using the Spring Roo Addon for Spring Data Graph and deploying the App to CloudFoundry.
7. What does NOSQL stand for?
It’s not “No to SQL”
It’s not “Never SQL”
8. What does NOSQL stand for?
It’s not “No to SQL”
It’s not “Never SQL”
It’s “Not Only SQL”
9. What does NOSQL stand for?
It’s not “No to SQL”
It’s not “Never SQL”
It’s “Not Only SQL”
NOSQL no-seek-wool n. Describes ongoing
trend where developers increasingly opt for
non-relational databases to help solve their
problems, in an effort to use the right tool for
the right job.
10. Why NOSQL now?
We have observed four trends:
๏ Trend 1: Size of data is growing
๏ Trend 2: Data is increasingly connected
๏ Trend 3: Data is increasingly semi-structured
๏ Trend 4: Change in architecture
12. NOSQL categories
We see four main categories in the NOSQL space:
Key-Value
•Redis
•Riak
•Voldemort
13. NOSQL categories
We see four main categories in the NOSQL space:
Column-family/
Key-Value
BigTable
•Redis
•Riak •Cassandra
•Voldemort •HBase
14. NOSQL categories
We see four main categories in the NOSQL space:
Column-family/
Key-Value
BigTable
•Redis
•Riak •Cassandra
•Voldemort •HBase
Document
•MongoDB
•CouchDB
15. NOSQL categories
We see four main categories in the NOSQL space:
Column-family/
Key-Value
BigTable
•Redis
•Riak •Cassandra
•Voldemort •HBase
Document Graph
•Neo4j
•MongoDB
•InfiniteGraph
•CouchDB
•OrientDB
•DEX
16. Scaling to size vs. Scaling to complexity
Size
Key-Value stores
Bigtable clones
Document databases
Graph databases
Complexity
8
17. Scaling to size vs. Scaling to complexity
Size
Key-Value stores
Bigtable clones
Document databases
Graph databases
Billions of nodes
and relationships
Complexity
8
18. Scaling to size vs. Scaling to complexity
Size
Key-Value stores
Bigtable clones
Document databases
Graph databases
Billions of nodes
and relationships
> 90% of use cases
Complexity
8
20. What is Spring Data
๏ VMWare/SpringSource initiative to give Spring developers easy
access to the emerging world of NOSQL, including:
• Non-relational databases
• MapReduce
• Grails NOSQL support
• Cross-store persistence
• Object Persistence Mapping Infrastructure
• Generic Repository Infrastructure
• upcoming Spring Roo add-ons
10
21. Spring Data projects
๏ Code is in SpringSource git repository:
• http://springsource.org/spring-data
• https://github.com/SpringSource/spring-data-*
๏ Includes:
• data-commons
• spring-data-graph-neo4j
• spring-data-{redis,riak}
• spring-data-mongo
• spring-data-jdbc
• spring-data-jpa
22. Spring Data Neo4j
๏ Focus on Spring Data Neo4j
๏ VMWare is collaborating with Neo Technology, the company behind
the Neo4j graph database.
๏ Improved programming model: Annotation-based
programming model for graph applications
๏ Cross-store persistence: Extend existing JPA application with
NOSQL persistence
๏ Spring Roo support: Add graph persistence with Roo add-on
26. Good Relationships
๏ the world is rich, messy and related data
๏ relationships are as least as important as the things they connect
๏ Graphs = Whole > Sum of all parts
๏ complex interactions
๏ always changing, change of structures as well
๏ Graph: Relationships are part of the data
๏ RDBMS: Relationships part of the fixed schema
16
27. Questions and Answers
๏ Complex Questions
๏ Answers lie between the lines (things)
๏ Locality of the information
๏ Global searches / operations very expensive
๏ constant query time, regardless of data volume
17
28. Categories ?
๏ Categories == Classes, Trees ?
๏ What if more than one category fits?
๏ Tags
๏ Categories vi relationships like „IS_A“
๏ any number, easy change
๏ „virtual“ Relationships - Traversals
๏ Category dynamically derived from queries
18
43. For example
WORKS_WITH
project: spring-data
name: Oliver name: Michael
44. For example
WORKS_WITH
project: spring-data
name: Oliver name: Michael
EM
PL
LIVES_IN
OY
E
D_
BY
city: Dresden
company: VMware country: DE
45. For example
name: Rod
KN
S OW
OW S
KN
WORKS_WITH
project: spring-data
name: Oliver name: Michael
EM
PL
LIVES_IN
OY
E
D_
BY
city: Dresden
company: VMware country: DE
46. For example
name: Rod
KN
S OW
OW S
KN
WORKS_WITH
project: spring-data
name: Oliver name: Michael
EM
PL
LIVES_IN
S
OY
LIKE
E
D_
BY
city: Dresden
food: Chinese
company: VMware country: DE
47. Best NOSQL Database for Spring ?
Why ? Explain !
•Written in Java
•Embeddable or standalone Server
•Schema-free - perfect for rich domains
•Fully transactional (ACID)
•Persistent to custom on-disk file structure
•Traversal speeds of 1,000+ hops per ms
•24/7 production since 2003
•Integrated indexing
•Plenthora of language bindings
50. Whiteboard friendly
Blog
Post BEL
ON
GS
_TO
Ally’s
Blog
WROTE
BE
LO
NG
NS
S_
W
O
OT
Blog
Allison WROTE Post 2
51. Whiteboard friendly
Blog
Post BEL
ON
GS
_TO
Ally’s
Blog
WROTE
BE
LO
NG
NS
S_
W
O
T O
Blog
Allison WROTE Post 2 CO
MM
EN
T_
OR
FO
R
COMMENT_F
Comment
Comment
52. Whiteboard friendly
Blog
Post BEL
ON
GS
_TO
Ally’s
Blog
WROTE
BE
LO
NG
NS
S_
W
O
T O
Blog
Allison WROTE Post 2 CO
MM
EN
T_
OR
FO
R
COMMENT_F
Comment
Comment
53. Show me some code, please
GraphDatabaseService graphDb =
new EmbeddedGraphDatabase(“var/neo4j”);
Node david = graphDb.createNode();
Node andreas = graphDb.createNode();
david.setProperty(“name”, “David Montag”);
andreas.setProperty(“name”, “Andreas Kollegger”);
Relationship presentedWith = david.createRelationshipTo(
andreas, PresentationTypes.PRESENTED_WITH);
presentedWith.setProperty(“date”, System.currentTimeMillis());
54. Show me some code, please
GraphDatabaseService graphDb =
new EmbeddedGraphDatabase(“var/neo4j”);
Transaction tx = graphDb.beginTx();
try {
Node david = graphDb.createNode();
Node andreas = graphDb.createNode();
david.setProperty(“name”, “David Montag”);
andreas.setProperty(“name”, “Andreas Kollegger”);
Relationship presentedWith = david.createRelationshipTo(
andreas, PresentationTypes.PRESENTED_WITH);
presentedWith.setProperty(“date”, System.currentTimeMillis());
tx.success();
} finally {
tx.finish();
}
61. Traversal framework
Example: a dependency graph
Query: Find all dependencies of A, transitively A
B
D
C
TraversalDescription desc = Traversal.description()
.relationships(ExampleTypes.DEPENDS_ON, Direction.OUTGOING);
Node a = ...;
for (Node dependency : desc.traverse(a).nodes()) {
print(dependency);
}
63. So how do I find a node
to traverse from?
g!
in
ex
i nd
i ng
us
B y ?
64. So how do I find a node
to traverse from?
g!
in
ex
i nd
i ng
us
B y name: David
?
65. So how do I find a node
to traverse from?
g!
in
ex
i nd
i ng
us
B y name: David
?
David
66. So how do I find a node
to traverse from?
g! Andreas
in
ex
i nd Michael
i ng
us
B y name: David
?
David
Ed
Allison
67. Cypher Query Language
๏ Declarative query language
• Describe what you want, not how
• Based on pattern matching
๏ Examples:
START david=node:people(name=”David M”) # index lookup
MATCH david-[:knows]-()-[:knows]-foaf
WHERE foaf.age > 18
RETURN foaf
START user=node(5, 15, 26, 28) # node IDs
MATCH user--friend
RETURN user, COUNT(friend), SUM(friend.money)
30
68. Cypher Query Language (E
xp
๏ Declarative query language en er
ta im
• Describe what you want, not how l)
• Based on pattern matching
๏ Examples:
START david=node:people(name=”David M”) # index lookup
MATCH david-[:knows]-()-[:knows]-foaf
WHERE foaf.age > 18
RETURN foaf
START user=node(5, 15, 26, 28) # node IDs
MATCH user--friend
RETURN user, COUNT(friend), SUM(friend.money)
30
69. Beyond basics
๏ Graph algorithm library
• Cheapest path (Dijkstra, A*)
• Shortest path
• Simple paths
• All paths
๏ REST API access to Neo4j Standalone Server
๏ High availability and online backups
• Provides fault tolerance and horizontal scaling of reads
31
71. Spring Framework Conveniences
๏ default enterprise development framework
๏ future Java Cloud stack
๏ POJO centric application design
๏ made AspectJ aspects socially acceptable (tx-config, @Configurable)
๏ Template programming model
๏ Inversion of Control / Dependency Injection
๏ Spring Java Config, configuration XML-namespaces
๏ lots of powerful libraries and library abstractions
๏ existing, well-known persistence framework for JDBC
๏ Spring Data project
72. Programming model overview
๏ SDN is the brain child of Rod Johnson and Emil Eifrém
• Wrote functional initial prototype
• Developed by Neo Technology and SpringSource teams
๏ Uses annotations to define POJO entities
๏ Entity state backed by graph database
๏ Two modes of Object Graph Mapping
• Spring Data Mapping
• seamless object mapping leverages AspectJ
๏ Spring Roo add-on available
73. Spring Data Neo4j features
๏ Annotation-based programming model
๏ Spring Data Commons Repository support
๏ Neo4j Query (Cypher, Gremlin) and Traversal support
• on dynamic fields and via repository methods
๏ Neo4j indexing support (includes fulltext and numeric range queries)
๏ Entity types stored in the graph database as well
๏ Dynamic type projection (duck typing)
๏ Cross-store support for partial JPA / graph entities
๏ Support for JSR-303 (bean validation)
๏ Support for the Neo4j Server (remote server and in server extension)
๏ Neo4jTemplate with exception translation, optional transaction management and
more
35
74. Classic Neo4j domain class
public class Actor {
private final Node underlyingNode;
Actor( final Node node ) {
underlyingNode = node;
}
public Node getUnderlyingNode() {
return underlyingNode;
}
public final String getName() {
return (String) underlyingNode.getProperty( “name” );
}
public void setName( final String name ) {
underlyingNode.setProperty( “name”, name );
}
}
75. Spring Data Neo4j domain class
@NodeEntity
public class Actor {
@Indexed
private String name;
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
76. What about relationships
@NodeEntity
class Actor {
...
public Iterable
<Movie> getMovi
final List<Movi es() {
e> movies = new
for ( Relations LinkedList<Movi
hip rel : under e>();
RelTypes.ACTS_I lyingNode.getRe
N, Direction.OU lationships(
movies.add( new TGOING ) ) {
Movie( rel.getE
Old
} ndNode() ) );
return movies;
}
class)
@RelatedTo(type="ACTS_ IN", elementClass = Movie.
;
private Set<Movie> movies
public Iterable<Movie> ge
tMovies() {
New
return movies;
}
78. Defining entity classes
• @NodeEntity
• Represents a node in the graph
• Fields saved as properties on node
• References stored as relationships between nodes
• Instantiated using Java ‘new’ keyword, like any POJO
• Also returned by lookup mechanisms
• Type information stored in the graph
80. Defining entity classes
• @RelationshipEntity
• Represents a relationship in the graph
• Fields saved as properties on relationship
• Special fields for start- and end-nodes
• Only returned by lookup methods
81. Fields in node entities (@NodeEntity)
• Primitive types and strings are directly persisted
• For all other types, Spring conversion support can be used
• Enum and Date conversion is provided out-of-the-box
• Transient fields not persisted
@NodeEntity
public class Actor {
private String name;
private int age;
private HairColor hairColor;
private transient String nickname;
}
41
82. Fields in node entities (@NodeEntity)
• Fields of types that represent a node (@NodeEntity)
42
83. Fields in node entities (@NodeEntity)
• Fields of types that represent a node (@NodeEntity)
@NodeEntity
public class Movie {}
@NodeEntity
public class Person {
private Movie favoriteMovie;
}
42
84. Fields in node entities (@NodeEntity)
• Fields of types that represent a node (@NodeEntity)
@NodeEntity
public class Movie {}
@NodeEntity
public class Person {
private Movie favoriteMovie;
}
@NodeEntity
public class Movie {
private Actor topActor;
}
@NodeEntity
public class Actor {
// Mirrors topActor in Movie
@RelatedTo(type = ”topActor”, direction = Direction.INCOMING)
private Movie wasTopActorIn;
}
42
85. Fields in node entities (@NodeEntity)
• Fields of collections of node entities: @RelatedTo
@NodeEntity
public class Movie {}
@NodeEntity
public class Actor {
@RelatedTo(type = “ACTS_IN”)
private Set<Movie> movies;
}
43
86. Fields in node entities (@NodeEntity)
๏ Fields of collections of relationship entities: @RelatedToVia
@RelationshipEntity
public class Role {
@StartNode private Actor actor;
@EndNode private Movie movie;
private String roleName;
}
@NodeEntity
public class Actor {
@RelatedToVia(type = “ACTS_IN”)
private Iterable<Role> roles;
}
๏ Read only view of relationship entities 44
87. Fields in relationship entities
(@RelationshipEntity)
• Primitive and convertible types work just the same
• @StartNode and @EndNode provide access to the start and
end node entities for the relationship entity
@RelationshipEntity
public class Role {
@StartNode private Actor actor;
@EndNode private Movie movie;
private String title;
}
88. Indexing
By annotating an entity field with @Indexed it becomes searchable:
@NodeEntity
public class Actor {
@Indexed private String name;
@Indexed private HairColor hairColor;
It can then be looked up:
GraphRepository<Actor> actorRepo =
template.repositoryFor(Actor.class);
Actor kevin =
actorRepo.findByPropertyValue(“name”, “Kevin Bacon”);
Iterable<Actor> allBlondActors =
actorRepo.findAllByPropertyValue(“hairColor”, “blond”);
89. Indexing
@NodeEntity
public class Actor {
@Indexed(type = FULLTEXT)
private String name;
๏ Index name defaults to domain class name
๏ Index key defaults to field name
๏ Fulltext and spatial index types
๏ Repository query methods for any Lucene query, including ranges:
Iterable<Actor> allKevinsOlderThan32 =
actorRepo.findAllByQuery(“name:Kevin* AND age>32”);
Iterable<Actor> youngActors =
actorRepo.findAllByRange(“age”, 3, 18);
90. Traversal
@NodeEntity
public class Actor {
@GraphTraversal(
traversalBuilder = CoactorsTraversalDescriptionBuilder.class)
private Iterable<Actor> coactors;
}
public class CoactorsTraversalDescriptionBuilder implements
FieldTraversalDescriptionBuilder {
public TraversalDescription build(...) {
return Traversal.description()
.evaluator(Evaluators.atDepth(2))
.relationships(RelTypes.ACTS_IN);
}
}
Example for dynamic field computation
48
91. Cypher query language
@NodeEntity
public class Actor {
@Query(“START actor=({self}) ” +
“MATCH (actor)-[:ACTS_IN]->(movie)<-[:ACTS_IN]-(coactor) ” +
“RETURN coactor”)
private Iterable<Actor> coactors;
}
@NodeEntity
public class Actor {
@Query(“START actor=({self}) ” +
“MATCH (actor)-[:ACTS_IN]->(movie)<-[:ACTS_IN]-(coactor) ” +
“RETURN movie.title, coactor.name”)
private Iterable<Map<String, Object>> movieCoactorPairs;
}
49
92. Spring-Data-Mapping
๏ Based on Spring-Data-Commons infrastructure
• Extract Mapping Meta Information
‣Neo4jPersistentEntity, Neo4jPersistentProperty
• Entity-Converter Implementations for Object-Graph-Mapping
‣Type-resolution
‣Entity construction
‣Transfer properties
‣loaed for eagerly fetched relationships
• Neo4j-Template for Graph-Interaction
50
93. AspectJ
๏ Introduces interface to entities:
• NodeBacked into @NodeEntity classes
• RelationshipBacked into @RelationshipEntity classes
๏ NodeBacked introduces methods such as:
• relateTo
• findByQuery
• findAllByTraversal
• ...
๏ going to be pulled out in separate Active-Record-Mixin
51
94. AspectJ - Tooling
๏ IDE‘s
• latest versions of STS / Eclipse with current AJDT plugin
• IntelliJ IDEA 10.5 compile + run, some editor quirks
‣full AspectJ support in IDEA 11
๏ Build Systems
• Maven
• Gradle
• Ant / Ivy
• ...
52
95. AspectJ - NodeBacked.relateTo
<T extends RelationshipBacked> T NodeBacked.relateTo(
NodeBacked node,
Class<T> relationshipEntityType,
String relationshipType
);
usage:
@NodeEntity
public class Actor {
public Role actsIn(Movie movie, String roleName) {
Role role = relateTo(movie, Role.class, “ACTS_IN”);
role.setName(roleName);
return role;
}
}
53
96. Interface based Repositories
๏ based on Repository infrastructure in Spring Data Commons
๏ just define the interface and the namespace configuration
๏ provide out-of-the-box support for
• CRUD-Operations
• Index-Lookups
• Traversal-Execution
• Graph-Queries (Cypher, Gremlin)
• derived Queries
• Spatial Queries
๏ extensible via custom methods with provided implementations
54
97. Repositories
interface MovieRepository extends GraphRepository<Movie> {
Movie findById(String id);
Page<Movie> findByTitle(String title, Pageable page);
}
<neo4j:repositories base-package=“com.example.repositories„/
@Controller
public class MovieController {
@Autowired MovieRepository moviesRepository;
@RequestMapping(value = "/movies/{movieId}",...)
public String show(Model model, @PathVariable String movieId) {
Movie movie = moviesRepository.findByPropertyValue("id", movieId);
Movie movie = moviesRepository.findById(movieId);
model.addAttribute("movie", movie);
return "/movies/show";
}}
55
99. Repository-Query-Support
interface MovieRepository extends GraphRepository<Movie> {
@Query("start m=({movie}) match m-[ACTS_IN]-actor return actor")
Iterable<Actor> getActorsCypher(@Param("movie") Movie m);
@Query("start movie =({0}) match (movie)<-[role:ACTS_IN]-(actor)
return actor.name, role.title")
Iterable<Map<String,Object>> getCast(Movie m);
@Query(value = "g.v(movie).out('ACTS_IN')", type = QueryType.Gremlin)
Iterable<Person> getActorsGremlin(@Param("movie") Movie m);
}
57
100. Neo4j-Template (I)
๏ well known Spring Template Pattern
๏ Resource / Transaction Management
๏ Convenience Methods
๏ Nodes and Entities handling & conversion
๏ Fluent Query Result Handling
๏ Works also via REST with Neo4j-Server
๏ Exception Translation
58
101. Neo4j-Template (II)
template.lookup("node", "name", "David")
.to(String.class, new PropertyContainerNameConverter()).single()
template.traverse(node, traversal)
.to(Integer.class,new ResultConverter<Path,Integer>() {
public Integer convert(Path path, Class<String> type) {
return path.length();
}})
template.query("start movie=(Movies,title, {m}) match movie-->actor return actor",
map("m","Matrix")).to(Actor.class)
template.execute("g.v(ref).outE", map("ref",0)).to(Relationship.class)
59
102. REST-Client-Support
<bean id="restGraphDatabaseService"
class="org.sf.data.neo4j.rest.SpringRestGraphDatabase">
<constructor-arg value="http://localhost:7473/db/data" />
</bean>
<datagraph:config graphDatabaseService="restGraphDatabaseService"/>
๏ drop-in replacement for the embedded GraphDatabase
๏ works transparently with POJO-Entity-Mapping and
Neo4j-Template
60
103. REST-Server-Support
public class HelloWorldInitializer extends SpringPluginInitializer {
public HelloWorldInitializer() {
super(new String[]{"spring/helloWorldServer-Context.xml"},
Pair.of("worldRepository", WorldRepository.class),
Pair.of("graphRepositoryFactory",
GraphRepositoryFactory.class));
}
}
๏ integrate Spring Data Neo4j config with already running
Graph-Database in Neo4j-Server
๏ expose Spring Beans as Jersey Injectables
61
105. A scenario...
You have a traditional web app using JPA to persist data to a relational
database
106. Option C: Introducing cross-store
persistence
๏ JPA data and NOSQL data can share a data model
๏ Could be the entire entity, or some fields of an entity
๏ We call this cross-store persistence
• One transaction managerdatabase the NOSQL database
with the JPA relational
to coordinate
• AspectJ support to manage the NOSQL entities and fields
107. The JPA data model
Restaurant UserAccount
@Entity @Entity
public class Restaurant { @Table(name = "user_account")
@Id @GeneratedValue public class UserAccount {
private Long id; @Id @GeneratedValue
private String name; private Long id;
private String city; private String userName;
private String state; private String firstName;
private String zipCode; private String lastName;
@Temporal(TemporalType.TIMESTAMP)
private Date birthDate;
@ManyToMany(cascade = CascadeType.ALL)
private Set<Restaurant> favorites;
108. Adding to the data model
Restaurant UserAccount
@Entity @Entity
@NodeEntity(partial = true) @Table(name = "user_account")
public class Restaurant { @NodeEntity(partial = true)
@Id @GeneratedValue public class UserAccount {
private Long id; @Id @GeneratedValue
private String name; private Long id;
private String city; private String userName;
private String state; private String firstName;
private String zipCode; private String lastName;
@Temporal(TemporalType.TIMESTAMP)
private Date birthDate;
@ManyToMany(cascade = CascadeType.ALL)
Recommendation private Set<Restaurant> favorites;
@RelationshipEntity @GraphProperty
public class Recommendation { String nickname;
@StartNode @RelatedTo(type = "friends",
private UserAccount user; elementClass = UserAccount.class)
@EndNode Set<UserAccount> friends;
private Restaurant restaurant; @RelatedToVia(type = "recommends",
private int stars; elementClass = Recommendation.class)
private String comment; Iterable<Recommendation> recommendations;
109. Adding to the data model
Restaurant UserAccount
@Entity @Entity
@NodeEntity(partial = true) @Table(name = "user_account")
public class Restaurant { @NodeEntity(partial = true)
@Id @GeneratedValue public class UserAccount {
private Long id; @Id @GeneratedValue
private String name; private Long id;
private String city; private String userName;
private String state; private String firstName;
private String zipCode; private String lastName;
@Temporal(TemporalType.TIMESTAMP)
private Date birthDate;
@ManyToMany(cascade = CascadeType.ALL)
Recommendation private Set<Restaurant> favorites;
@RelationshipEntity @GraphProperty
public class Recommendation { String nickname;
@StartNode @RelatedTo(type = "friends",
private UserAccount user; elementClass = UserAccount.class)
@EndNode Set<UserAccount> friends;
private Restaurant restaurant; @RelatedToVia(type = "recommends",
private int stars; elementClass = Recommendation.class)
private String comment; Iterable<Recommendation> recommendations;
110. Adding to the data model
Restaurant UserAccount
@Entity @Entity
@NodeEntity(partial = true) @Table(name = "user_account")
public class Restaurant { @NodeEntity(partial = true)
@Id @GeneratedValue public class UserAccount {
private Long id; @Id @GeneratedValue
private String name; private Long id;
private String city; private String userName;
private String state; private String firstName;
private String zipCode; private String lastName;
@Temporal(TemporalType.TIMESTAMP)
private Date birthDate;
@ManyToMany(cascade = CascadeType.ALL)
Recommendation private Set<Restaurant> favorites;
@RelationshipEntity @GraphProperty
public class Recommendation { String nickname;
@StartNode @RelatedTo(type = "friends",
private UserAccount user; elementClass = UserAccount.class)
@EndNode Set<UserAccount> friends;
private Restaurant restaurant; @RelatedToVia(type = "recommends",
private int stars; elementClass = Recommendation.class)
private String comment; Iterable<Recommendation> recommendations;
111. Adding to the data model
Restaurant UserAccount
@Entity @Entity
@NodeEntity(partial = true) @Table(name = "user_account")
public class Restaurant { @NodeEntity(partial = true)
@Id @GeneratedValue public class UserAccount {
private Long id; @Id @GeneratedValue
private String name; private Long id;
private String city; private String userName;
private String state; private String firstName;
private String zipCode; private String lastName;
@Temporal(TemporalType.TIMESTAMP)
private Date birthDate;
@ManyToMany(cascade = CascadeType.ALL)
Recommendation private Set<Restaurant> favorites;
@RelationshipEntity @GraphProperty
public class Recommendation { String nickname;
@StartNode @RelatedTo(type = "friends",
private UserAccount user; elementClass = UserAccount.class)
@EndNode Set<UserAccount> friends;
private Restaurant restaurant; @RelatedToVia(type = "recommends",
private int stars; elementClass = Recommendation.class)
private String comment; Iterable<Recommendation> recommendations;
112. Adding to the data model
Restaurant UserAccount
@Entity @Entity
@NodeEntity(partial = true) @Table(name = "user_account")
public class Restaurant { @NodeEntity(partial = true)
@Id @GeneratedValue public class UserAccount {
private Long id; @Id @GeneratedValue
private String name; private Long id;
private String city; private String userName;
private String state; private String firstName;
private String zipCode; private String lastName;
@Temporal(TemporalType.TIMESTAMP)
private Date birthDate;
@ManyToMany(cascade = CascadeType.ALL)
Recommendation private Set<Restaurant> favorites;
@RelationshipEntity @GraphProperty
public class Recommendation { String nickname;
@StartNode @RelatedTo(type = "friends",
private UserAccount user; elementClass = UserAccount.class)
@EndNode Set<UserAccount> friends;
private Restaurant restaurant; @RelatedToVia(type = "recommends",
private int stars; elementClass = Recommendation.class)
private String comment; Iterable<Recommendation> recommendations;
113. Spring Data Neo4j Roo add-on
๏ Roo adding support for non-JPA
persistence providers
๏ Spring Data Neo4j was the first
NOSQL persistence Roo
Add-On
๏ See the chapter on Spring Data
Neo4j in the latest O’Reilly
Roo book, Getting Started with
Roo.
67
114. Spring Data Neo4j Roo add-on
roo> project --topLevelPackage org.neo4j.imdb
roo> graph setup --provider NEO4J --databaseLocation target/imdb
roo> graph entity --class ~.model.Movie
roo> field string title
roo> field number --fieldName year --type java.lang.Integer --permitReservedWords --primitive
roo> graph entity --class ~.model.Actor
roo> field string name
roo> graph relationship --to Movie --from Actor --fieldName movies --type ACTS_IN
--cardinality ONE_TO_MANY
roo> graph relationship --via ~.model.Role --to Movie --from Actor --fieldName roles
--type ACTS_IN --cardinality ONE_TO_MANY
roo> graph relationship --from Movie --to Actor --type ACTS_IN --fieldName actors
--direction INCOMING --cardinality MANY_TO_ONE
roo> field string --fieldName title --class ~.model.Role
roo> controller scaffold --class ~.web.ActorController --entity ~.model.Actor
roo> controller scaffold --class ~.web.MovieController --entity ~.model.Movie
68
115. Spring Data Neo4j Guidebook
“Good Relationships”
“I’m excited about Spring Data Neo4j.... Spring Data Neo4j makes working
with Neo4j amazingly easy, and therefore has the potential to make you
more successful as a developer.”
Rod Johnson, founder of Spring
๏ Spring Data Neo4j comes with a great Guide Book, featuring:
• Forewords by Rod Johnson and Emil Eifrem
• An easy to read, narrative tutorial walkthrough for cineasts.net
• A comprehensive reference for all the details
• Check it out here: http://spring.neo4j.org/guide
69
116. The end (and the beginning!)
๏ See the Spring Data Neo4j site for more info:
http://spring.neo4j.org
๏ Check out the developer notes at GitHub:
http://spring.neo4j.org/notes
๏ Again, don’t miss our fantastic e-book on Spring Data Neo4j:
http://spring.neo4j.org/guide
๏ Spring Data Forum at
http://spring.neo4j.org/discussions
๏ All about Neo4j:
http://neo4j.org
๏ Neo4j videos and webinars:
http://video.neo4j.org
social networks (our actions in them work life health)\nthe internet\nits hardware\nits software\nour interactions\nour body\nnature environment\npolitical economic networks\nzusammenhaenge\nhistory\nscience\nzeit gr&#xFC;nen abgeordneter handy\n
social networks (our actions in them work life health)\nthe internet\nits hardware\nits software\nour interactions\nour body\nnature environment\npolitical economic networks\nzusammenhaenge\nhistory\nscience\nzeit gr&#xFC;nen abgeordneter handy\n
messy world\nfast changing world\nbez um graph sind teil der daten\nim rdbms teil des starren schemas\nkomplexe zusammenhaenge\nkomplexe fragen\nimmer neue kategorien - rels\ndynamisch - traversals\ntags attribute\ntemporale attribute\ndyn sprachen besser geeignet \n
messy world\nfast changing world\nbez um graph sind teil der daten\nim rdbms teil des starren schemas\nkomplexe zusammenhaenge\nkomplexe fragen\nimmer neue kategorien - rels\ndynamisch - traversals\ntags attribute\ntemporale attribute\ndyn sprachen besser geeignet \n
messy world\nfast changing world\nbez um graph sind teil der daten\nim rdbms teil des starren schemas\nkomplexe zusammenhaenge\nkomplexe fragen\nimmer neue kategorien - rels\ndynamisch - traversals\ntags attribute\ntemporale attribute\ndyn sprachen besser geeignet \n
\n
\n
\n
\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
Neo4j is a graph database. \n\nNodes, rels, key-value props on nodes and rels.\n
... so like I&#x2019;m a node, Thomas is a node, and there&#x2019;s a PRESENTED_WITH relationship between us.\n
... so like I&#x2019;m a node, Thomas is a node, and there&#x2019;s a PRESENTED_WITH relationship between us.\n
... so like I&#x2019;m a node, Thomas is a node, and there&#x2019;s a PRESENTED_WITH relationship between us.\n
... so like I&#x2019;m a node, Thomas is a node, and there&#x2019;s a PRESENTED_WITH relationship between us.\n
... so like I&#x2019;m a node, Thomas is a node, and there&#x2019;s a PRESENTED_WITH relationship between us.\n
... so like I&#x2019;m a node, Thomas is a node, and there&#x2019;s a PRESENTED_WITH relationship between us.\n
... so like I&#x2019;m a node, Thomas is a node, and there&#x2019;s a PRESENTED_WITH relationship between us.\n
schema-free evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
evolve data separately\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
Traversing is great, but it needs to start from somewhere. How do we find that place?\n
\n
\n
\n
No need for persistence contexts or entity managers.\n\n
No need for persistence contexts or entity managers.\n\n
\n
Jumping right into code\n
\n
\n
\n
\n
Anonymous relationships\n
Anonymous relationships\n
Anonymous relationships\n
Anonymous relationships\n
Anonymous relationships\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
This does not apply to Neo4j.\nIn Neo4j, transactions MUST be used.\n