Drivers & Language Guides
How to connect to Neo4j?
To build an application, you want to connect to Neo4j from your technology stack. Fortunately it is very easy using a driver which connects to Neo4j via Bolt or Http.
The binary Bolt Protocol
Starting with Neo4j 3.0 we support a binary protocol called Bolt. It is based on the PackStream serialization and supports the Cypher type system, protocol versioning, authentication and TLS via certificates. For Neo4j Clusters, Bolt provides smart client routing with load balancing and failover.
The binary protocol is enabled in Neo4j by default, so you can use any language driver that supports it.
You can find detailed information about the official drivers in the Neo4j Driver Manual
For more details on the protocol implementation, see the implementers documentation.
All Neo4j Drivers
Thanks to the Neo4j contributor community, there are additionally drivers for almost every popular programming language, most of which mimic existing database driver idioms and approaches. Get started with your stack now, see the dedicated page for more detail.
Example Project Description
To demonstrate connection to and usage of Neo4j in different programming languages we’ve created an example application. It is a simple, one-page webapp, that uses Neo4j’s movie demo database (movie, actor, director) as data set. The same front-end web page in all applications consumes 3 REST endpoints provided by backend implemented in the different programming languages and drivers.
- movie search by title
- single movie listing
- graph visualization of the domain
Using the HTTP API
If you want to access Neo4j programmatically, you can also use the HTTP-API, which allow you to:
- POST one or more Cypher statements with parameters
- Keep transactions open over multiple requests
- Choose different result formats
Let’s look at one of the underlying remote API endpoint that Neo4j offers to execute queries. These APIs can be then used directly via a HTTP library or a driver for your language.
A simple HTTP Cypher request, executable in the Neo4j Browser would look like this:
Some of the language drivers use the HTTP API under the hood, but make them available in a more convenient way.