Neo4j server supporting multiple graph databases

[brian]

Hello,

I know that this topic has been discussed before (e.g. https://groups.google.com/d/msg/neo4j/3LbQ1MlrEm4/iZhuZeRTW6YJ), but I wanted to lend my support and use cases to this request. I find the fact that the Neo4j server does not support multiple graph DBs to be very limiting.  Here are a few use-cases:

• In a development environment I want to have a test-mode database and a development-mode database on a single machine.  Unit and functional tests are run against the test-mode database so that data in the development-mode database (which mimics production-mode) is not disturbed.  This is fairly common in, for example, Ruby on Rails development environments.  Right now, I'm forced to install two Neo4j server instances each running on different ports and manage separate configurations for those instances.
• In a production environment, I want to have separate graph DBs for unrelated data. For example, I might want to have one graph DB for application data and another one for "administrative data" such as session information, statistics, etc.  The data is unrelated and I will never construct a query across these separate graph DBs.
• Multi-tenancy.  I'm hosting data from several different users or applications that is unrelated. Again, I will never construct a query across these graph DBs.

I'm sure there are more use-cases.  I know that the above can be simulated using Tinkerpop partitions, however I don't want to add yet another component into the mix.  Custom Node/Relationships properties or labels (in 1.9) could be used, but this forces me to write a persistence layer to manage this.

So really the best solution would be to have the Neo4j server manage these namespaces including making the Neo4j console and Monitoring/Management Web interface "namespace aware" as well as making these namespaces addressable via the REST API.  This is fairly common in RDBMSes.  You typically don't install multiple instances of the DB server.  You define multiple schemas, databases, or table spaces all managed by a single DB server instance.

Thanks.

-brian

[Philip Rathle]

HI Brian,

This is on the roadmap, but there are a number of things ahead of it, so it's not likely to be this year. Thanks for the vote-up though... I agree that it will be very useful to be able to manage multiple/ independent graphs/namespaces in a single database instance.

Philip

-brian

--
You received this message because you are subscribed to the Google Groups "Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Sander Elias]

We are a few years ahead now, what is the current status on multiple DB's?

[hmal...@calliduscloud.com]

Another year!. 

Any update on this one?

On Wednesday, March 15, 2017 at 2:05:54 PM UTC-7, Sander Elias wrote:

We are a few years ahead now, what is the current status on multiple DB's?

[Michael Hunger]

We chose to work on some other issues first, but the multi-graph / multi-tenancy / graph-views topics has been a lot in discussion lately. 

So while it won't be in 3.2 I'm sure we'll see a suitable variant in the next releases.

Michael

--
You received this message because you are subscribed to the Google Groups "Neo4j" group.

To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.