Hi, Im am unsure about bolt+routing vs neo4j
Consideration about routing tables on multi-data center deployments - Knowledge Base, How Neo4j Browser uses bolt+routing - Knowledge Base
Mentions bolt+routing - but it's valid up to 4.4
The course: Building Neo4j Applications with Python says:
Most likely, you will use a variation of the neo4j scheme within your connection string.
neo4j - Creates an unencrypted connection to the DBMS. If you are connecting to a local DBMS or have not explicitly turned on encryption then this is most likely the option you are looking for.
neo4j+s - Creates an encrypted connection to the DBMS. The driver will verify the authenticity of the certificate and fail to verify connectivity if there is a problem with the certificate.
neo4j+ssc - Creates an encrypted connection to the DBMS, but will not attempt to verify the authenticity of the certificate.
Variations of the bolt scheme can be used to connect directly to a single DBMS (within a clustered environment or standalone). This can be useful if you have a single server configured for data science or analytics.
bolt - Creates an unencrypted connection directly to a single DBMS.
bolt+s - Creates an encrypted connection directly to a single DBMS and verify the certificate.
bolt+ssc - Creates an encrypted connection to directly to a single DBMS but will not attempt to verify the authenticity of the certificate.
Has bolt+routing been raplaced - and isn't available anymore? I didn't find info in Breaking changes between Neo4j 4.4 and Neo4j 5.x - Upgrade and Migration Guide
Bye
Michael
@zweite.tontaube
Michael
bolt+routing was the original protocal and it only worked in a clustered environment. Do you currently have a cluster? If you used 'bolt+routing' on a single instance it would fail, and with some error related to could not get routing address of some such.
neo4j was then created to replace / enhance such that this single protocal would work whether in a single Neo4j installation or a Neo4j clustered installation.
In this case neo4j is effectively the one size fits all, for example if you develop in a environment of a single server use neo4j and if you then need to migrate your code to a clustered environment nothing needs to change.
Whereas previously if you developed in a single environment one would use bolt for it was the only protocal to work for single instances and then when you moved to a clustered environment you would need to change all your bolt references to bolt+routing
neo4j protocol eliminates the need to change as it works everywhere
1 Like
No, I am studying to take the Exam. That's why I'll ask many questions in the next few days...
On the one hand I think it will be easy - on the other I might shoot myself in the foot because of detailled knowledge which makes me answer questions differently than they are intended...
Since when has bolt+routing been replaced, i.e. "how far back" do I need to go: Introduction - Upgrade and Migration Guide
@zweite.tontaube
The neo4j:// scheme replaces bolt+routing:// and can be used for both clustered
and single-instance configurations. This is a rename only, and neo4j:// URIs can still
be used to communicate with Neo4j 3.x clusters.
1 Like
