Better understanding neo4j 5 composite databases

I've read through Introduction - Operations Manual

Is there any way to perform cross-database queries (read from one db, write nodes into another) without first configuring composite databases?

Is the CREATE ALIAS impossible without first creating a composite db?

As I read it composite database is simply a namespace for creating aliases and dont contain any data. Would it be accurate to say if I were to later DROP COMPOSITE DATABASE it is only making the aliases (and thus cross-db queries) unavailable, and has no impact on any nodes/relationships?

Trying to understand the possible impacts of choosing to setup a composite n4j database, and what ramifications it could have later on.

Thanks!

Hi @pdrangeid,

Is there any way to perform cross-database queries (read from one db, write nodes into another) without first configuring composite databases?

So a composite database acts as a layer that connects the multiple databases into a single one. Without composite database you cannot perform cross-database operations.

Is the CREATE ALIAS impossible without first creating a composite db?

The CREATE ALIAS command is used only in the composite db and therefore it does not make sense to be and cannot be used without creating it first.

As I read it composite database is simply a namespace for creating aliases and dont contain any data. Would it be accurate to say if I were to later DROP COMPOSITE DATABASE it is only making the aliases (and thus cross-db queries) unavailable, and has no impact on any nodes/relationships?

Exactly, you will not be able to perform cross-database operations but it does not have affect on the already committed operations.

I hope that I could help you understand better.

Best regards,
busymo

Thanks for the quick response! That helps clear it up.

Anyone from Neo4j: Are there any current plans for graphacademy or webinars on best practices, and/or optimizing cross-database query designs?

Thank-you!