Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
giuseppe-trisciuoglio avatar

Spring Data Neo4j

  • 1.8k installs
  • 318 repo stars
  • Updated June 22, 2026
  • giuseppe-trisciuoglio/developer-kit

How to integrate Neo4j graph databases into Spring Boot applications using entity mapping, repositories, and Cypher queries

About

Spring Data Neo4j provides patterns for integrating Neo4j graph databases into Spring Boot applications. Developers use it to define node entities with @Node annotation, configure imperative or reactive repositories, write custom Cypher queries with @Query, and manage relationships with @Relationship. The skill covers entity design with immutable fields, repository patterns for simple and complex queries, and testing strategies using embedded Neo4j databases via Neo4j Harness for integration tests.

  • Define node entities with @Node and relationships with @Relationship annotations
  • Create imperative (Neo4jRepository) or reactive (ReactiveNeo4jRepository) repositories with query derivation and custom
  • Write parameterized Cypher queries using $paramName syntax to prevent injection and filter graph patterns
  • Configure Spring Boot connection pooling, credentials, and Cypher-DSL dialect for Neo4j 5+ compatibility
  • Test with embedded Neo4j databases using @DataNeo4jTest and Neo4j Harness with Cypher fixtures

Spring Data Neo4j by the numbers

  • 1,808 all-time installs (skills.sh)
  • +142 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #271 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

spring-data-neo4j capabilities & compatibility

Capabilities
define immutable node entities with @node and @p · configure imperative and reactive repositories w · write parameterized cypher queries with @query a · test with embedded neo4j databases and cypher fi · manage relationship traversal with direction.inc · handle transaction boundaries with @transactiona
Use cases
database · api development · testing
Platforms
macOS · Windows · Linux
Runs
Runs locally
Pricing
Free
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill spring-data-neo4j

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.8k
repo stars318
Security audit3 / 3 scanners passed
Last updatedJune 22, 2026
Repositorygiuseppe-trisciuoglio/developer-kit

What it does

Integrate Neo4j graph database with Spring Boot via entity mapping, repositories, and Cypher queries

Who is it for?

Graph database backends, social networks, recommendation engines, knowledge graphs, and relationship-heavy domain models in Spring Boot

Skip if: Relational database integration (use Spring Data JPA), simple CRUD operations without graph traversal, applications requiring lazy-loaded relationships by default

When should I use this skill?

Building data access layer for Neo4j, defining entity relationships, writing graph traversal queries, setting up integration tests with embedded databases

What you get

Working Spring Boot integration with persisted graph entities, type-safe repositories, and custom Cypher queries tested against embedded Neo4j

  • Node entity classes with @Node and @Relationship annotations
  • Repository interfaces extending Neo4jRepository or ReactiveNeo4jRepository
  • Custom Cypher queries with @Query and parameterized syntax

By the numbers

  • Supports both imperative blocking and reactive non-blocking operations via separate repository interfaces
  • Provides @DataNeo4jTest annotation for focused integration test slicing with embedded Neo4j
  • Enables parameter injection in Cypher queries using $paramName syntax to prevent injection attacks

Files

SKILL.mdMarkdownGitHub ↗

Spring Data Neo4j Integration Patterns

Overview

Provides Spring Data Neo4j integration patterns for Spring Boot applications. Covers node entity mapping with @Node and @Relationship, repository configuration (imperative and reactive), custom Cypher queries with @Query, and integration testing with embedded Neo4j databases.

When to Use

Use this skill when working with:

  • Graph databases and Neo4j integration in Spring Boot
  • Node entities, relationships, and Cypher queries
  • Spring Data Neo4j repositories (imperative or reactive)
  • Neo4j testing with embedded databases

Instructions

1. Set Up Spring Data Neo4j

Add the dependency:

Maven:

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-data-neo4j</artifactId>
</dependency>

Gradle:

implementation 'org.springframework.boot:spring-boot-starter-data-neo4j'

Configure connection in application.properties:

spring.neo4j.uri=bolt://localhost:7687
spring.neo4j.authentication.username=neo4j
spring.neo4j.authentication.password=secret

Configure Cypher-DSL dialect (recommended):

@Configuration
public class Neo4jConfig {
    @Bean
    Configuration cypherDslConfiguration() {
        return Configuration.newConfig()
            .withDialect(Dialect.NEO4J_5).build();
    }
}
Validation Checkpoint: Run MATCH (n) RETURN count(n) via cypher-shell to verify the connection works before proceeding.

2. Define Node Entities

1. Use `@`Node annotation to mark entity classes 2. Choose ID strategy:

  • Business key as @Id (immutable, natural identifier)
  • Generated @Id @GeneratedValue (Neo4j internal ID)

3. Define relationships with @Relationship annotation 4. Keep entities immutable with final fields 5. Use `@`Property for custom property names

Validation Checkpoint: If entity save fails, check for constraint violations—duplicate IDs violate uniqueness constraints.

3. Create Repositories

1. Extend repository interface:

  • Neo4jRepository<Entity, ID> for imperative operations
  • ReactiveNeo4jRepository<Entity, ID> for reactive operations

2. Use query derivation for simple queries 3. Apply `@`Query annotation for complex Cypher queries 4. Use `$`paramName syntax for parameters

Validation Checkpoint: Test repository with findAll() first—if empty, verify the Neo4j instance is running and credentials are correct.

4. Test Your Implementation

1. Use `@`DataNeo4jTest for repository testing with test slicing 2. Set up Neo4j Harness with embedded database and fixtures 3. Provide test data via withFixture() Cypher queries 4. Clean up test data between tests

Validation Checkpoint: If tests fail with "Connection refused", ensure the embedded Neo4j started successfully in @BeforeAll.

Basic Entity Mapping

Node Entity with Business Key

@Node("Movie")
public class MovieEntity {

    @Id
    private final String title;  // Business key as ID

    @Property("tagline")
    private final String description;

    private final Integer year;

    @Relationship(type = "ACTED_IN", direction = Direction.INCOMING)
    private List<Roles> actorsAndRoles = new ArrayList<>();

    @Relationship(type = "DIRECTED", direction = Direction.INCOMING)
    private List<PersonEntity> directors = new ArrayList<>();

    public MovieEntity(String title, String description, Integer year) {
        this.title = title;
        this.description = description;
        this.year = year;
    }
}

Node Entity with Generated ID

@Node("Movie")
public class MovieEntity {

    @Id @GeneratedValue
    private Long id;

    private final String title;

    @Property("tagline")
    private final String description;

    public MovieEntity(String title, String description) {
        this.id = null;  // Never set manually
        this.title = title;
        this.description = description;
    }

    // Wither method for immutability with generated IDs
    public MovieEntity withId(Long id) {
        if (this.id != null && this.id.equals(id)) {
            return this;
        } else {
            MovieEntity newObject = new MovieEntity(this.title, this.description);
            newObject.id = id;
            return newObject;
        }
    }
}

Repository Patterns

Basic Repository Interface

@Repository
public interface MovieRepository extends Neo4jRepository<MovieEntity, String> {

    // Query derivation from method name
    MovieEntity findOneByTitle(String title);

    List<MovieEntity> findAllByYear(Integer year);

    List<MovieEntity> findByYearBetween(Integer startYear, Integer endYear);
}

Reactive Repository

@Repository
public interface MovieRepository extends ReactiveNeo4jRepository<MovieEntity, String> {

    Mono<MovieEntity> findOneByTitle(String title);

    Flux<MovieEntity> findAllByYear(Integer year);
}

Imperative vs Reactive:

  • Use Neo4jRepository for blocking, imperative operations
  • Use ReactiveNeo4jRepository for non-blocking, reactive operations
  • Do not mix imperative and reactive in the same application
  • Reactive requires Neo4j 4+ on the database side

Custom Queries with @Query

@Repository
public interface AuthorRepository extends Neo4jRepository<Author, Long> {

    @Query("MATCH (b:Book)-[:WRITTEN_BY]->(a:Author) " +
           "WHERE a.name = $name AND b.year > $year " +
           "RETURN b")
    List<Book> findBooksAfterYear(@Param("name") String name,
                                   @Param("year") Integer year);

    @Query("MATCH (b:Book)-[:WRITTEN_BY]->(a:Author) " +
           "WHERE a.name = $name " +
           "RETURN b ORDER BY b.year DESC")
    List<Book> findBooksByAuthorOrderByYearDesc(@Param("name") String name);
}

Custom Query Best Practices:

  • Use $parameterName for parameter placeholders
  • Use @Param annotation when parameter name differs from method parameter
  • MATCH specifies node patterns and relationships
  • WHERE filters results
  • RETURN defines what to return

Testing Strategies

Neo4j Harness for Integration Testing

Test Configuration:

@DataNeo4jTest
class BookRepositoryIntegrationTest {

    private static Neo4j embeddedServer;

    @BeforeAll
    static void initializeNeo4j() {
        embeddedServer = Neo4jBuilders.newInProcessBuilder()
            .withDisabledServer()  // No HTTP access needed
            .withFixture(
                "CREATE (b:Book {isbn: '978-0547928210', " +
                "name: 'The Fellowship of the Ring', year: 1954})" +
                "-[:WRITTEN_BY]->(a:Author {id: 1, name: 'J. R. R. Tolkien'}) " +
                "CREATE (b2:Book {isbn: '978-0547928203', " +
                "name: 'The Two Towers', year: 1956})" +
                "-[:WRITTEN_BY]->(a)"
            )
            .build();
    }

    @AfterAll
    static void stopNeo4j() {
        embeddedServer.close();
    }

    @DynamicPropertySource
    static void neo4jProperties(DynamicPropertyRegistry registry) {
        registry.add("spring.neo4j.uri", embeddedServer::boltURI);
        registry.add("spring.neo4j.authentication.username", () -> "neo4j");
        registry.add("spring.neo4j.authentication.password", () -> "null");
    }

    @Autowired
    private BookRepository bookRepository;

    @Test
    void givenBookExists_whenFindOneByTitle_thenBookIsReturned() {
        Book book = bookRepository.findOneByTitle("The Fellowship of the Ring");
        assertThat(book.getIsbn()).isEqualTo("978-0547928210");
    }
}

Examples

Example 1: Saving and Retrieving Entities

Input:

MovieEntity movie = new MovieEntity("The Matrix", "Welcome to the Real World", 1999);
movieRepository.save(movie);

MovieEntity found = movieRepository.findOneByTitle("The Matrix");

Output:

MovieEntity{
    title="The Matrix",
    description="Welcome to the Real World",
    year=1999,
    actorsAndRoles=[],
    directors=[]
}

Example 2: Custom Cypher Query

Input:

List<Book> books = authorRepository.findBooksAfterYear("J.R.R. Tolkien", 1950);

Output:

[
    Book{isbn="978-0547928210", name="The Fellowship of the Ring", year=1954},
    Book{isbn="978-0547928203", name="The Two Towers", year=1956},
    Book{isbn="978-0547928227", name="The Return of the King", year=1957}
]

Example 3: Relationship Traversal

Input:

@Query("MATCH (m:Movie)<-[:ACTED_IN]-(a:Person) " +
       "WHERE m.title = $title RETURN a.name as actorName")
List<String> findActorsByMovieTitle(@Param("title") String title);

List<String> actors = movieRepository.findActorsByMovieTitle("The Matrix");

Output:

["Keanu Reeves", "Laurence Fishburne", "Carrie-Anne Moss", "Hugo Weaving"]

---

Progress from basic to advanced examples covering complete movie database, social network patterns, e-commerce product catalogs, custom queries, and reactive operations.

See examples for comprehensive code examples.

Best Practices

Entity Design

  • Use immutable entities with final fields
  • Choose between business keys (@Id) or generated IDs (@Id @GeneratedValue)
  • Keep entities focused on graph structure, not business logic
  • Use proper relationship directions (INCOMING, OUTGOING, UNDIRECTED)

Repository Design

  • Extend Neo4jRepository for imperative or ReactiveNeo4jRepository for reactive
  • Use query derivation for simple queries
  • Write custom @Query for complex graph patterns
  • Don't mix imperative and reactive in same application

Configuration

  • Always configure Cypher-DSL dialect explicitly
  • Use environment-specific properties for credentials
  • Never hardcode credentials in source code
  • Configure connection pooling based on load

Testing

  • Use Neo4j Harness for integration tests
  • Provide test data via withFixture() Cypher queries
  • Use @DataNeo4jTest for test slicing
  • Test both successful and edge-case scenarios

Architecture

  • Use constructor injection exclusively
  • Separate domain entities from DTOs
  • Follow feature-based package structure
  • Keep domain layer framework-agnostic

Security

  • Use Spring Boot property overrides for credentials
  • Configure proper authentication and authorization
  • Validate input parameters in service layer
  • Use parameterized queries to prevent Cypher injection

Constraints and Warnings

  • Do not mix imperative and reactive repositories in the same application.
  • Neo4j transactions are required for write operations; ensure @Transactional is properly configured.
  • Be cautious with deep relationship traversal as it can cause performance issues.
  • Large result sets should be paginated to avoid memory problems.
  • Cypher queries are case-sensitive; ensure consistent casing in property names.
  • Immutable entities require proper wither methods for generated IDs.
  • Relationships in Spring Data Neo4j are not lazy-loaded by default; consider projection for large graphs.
  • The Neo4j Java driver is not compatible with reactive streams; use the reactive driver for reactive operations.

Troubleshooting

ProblemCauseSolution
Connection refused on localhost:7687Neo4j server not runningStart Neo4j or use embedded Neo4j for tests
Authentication failedWrong credentialsCheck spring.neo4j.authentication.username/password
Entity not saved / MATCH returns nothingTransaction not committedAdd @Transactional or verify auto-commit settings
ConstraintViolationException on saveDuplicate @Id valueEnsure IDs are unique or use @GeneratedValue
Relationships missing in resultsWrong @Relationship directionCheck Direction.INCOMING/OUTGOING/UNDIRECTED
@Query returns wrong dataCypher parameter syntaxUse $paramName not $ {paramName}
Test fails with @DataNeo4jTestEmbedded Neo4j not startedEnsure @BeforeAll starts Neo4j before tests

References

For detailed documentation including complete API reference, Cypher query patterns, and configuration options:

  • Annotations Reference
  • Cypher Query Language
  • Configuration Properties
  • Repository Methods
  • Projections and DTOs
  • Transaction Management
  • Performance Tuning

External Resources

Related skills

Forks & variants (1)

Spring Data Neo4j has 1 known copy in the catalog totaling 22 installs. They canonicalize to this original listing.

How it compares

Pick spring-data-neo4j for Spring Boot graph ORM patterns; use raw Neo4j driver skills when Spring Data abstractions are not in the stack.

FAQ

Should I use business keys or generated IDs as @Id?

Use business keys (@Id without @GeneratedValue) for immutable, natural identifiers. Use @Id @GeneratedValue for system-generated IDs, but implement wither methods for immutability.

Can I mix imperative and reactive repositories in the same application?

No. Do not mix imperative (Neo4jRepository) and reactive (ReactiveNeo4jRepository) in the same application. Choose one consistently.

Why are my relationships not appearing in query results?

Check the @Relationship direction (INCOMING, OUTGOING, UNDIRECTED) and verify the Cypher query MATCH pattern includes the relationship traversal explicitly.

Is Spring Data Neo4j safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.