Skip to content

neo4j-examples/sdn-migration

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

From SDN/OGM to Reactive SDN and beyond

Target audience

If you are a developer working on a Spring Data Neo4j (5) / OGM (SDN/OGM in short) application and want to upgrade to the latest Spring Data Neo4j, this migration repository is for you.

Application

The application maps movies and actors from the built-in Neo4j movie dataset.

Structure

The tip of each of the following branches define the desired state of the application for the corresponding migration step. Feel free to browse the code in each of these branches to see the code changes that have been made.

Note

If you are only interested in the high-level changes that such a migration entails, feel free to skip the rest of this documentation and read this instead.

  • the "first step" branch, a.k.a. step1_sdn-ogm_imperative, contains the initial SDN/OGM application.

  • the "second step" branch, a.k.a. step2_sdn_imperative, illustrates the upgrade from a typical Spring Data Neo4j / OGM application to the latest Spring Data Neo4j, without reactive support. Most of the existing APIs are mapped one-to-one. This is the first recommended step to follow when you start a migration.

  • The "final step" and default branch, a.k.a. step3_sdn_reactive, includes the final state of the project. The project uses, in that case, the latest Spring Data Neo4j version and relies on its reactive programming support.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages