Databases
Managed Neo4j on your own cluster
Graph database for connected data: relationships as first-class records, traversed with Cypher over Bolt and HTTP.
Created inside a project, beside the apps that use it. Each project gets its own instance, storage and credentials.
01What it does
Neo4j, run for you
Neo4j Community Edition on Neo4j's own chart.
For data whose shape is the relationships: recommendations, permissions, fraud rings, dependency graphs. Neo4j stores the edges as records of their own and traverses them with Cypher, and bound apps get a Bolt URI beside the HTTP port, username and password.
The page cache above the heap is what keeps traversals fast, which is why the smallest size starts at 2Gi, the chart's own floor. The disk for the graph and its transaction logs is chosen once, at creation.
02Options
What you choose
What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.
- Sizes
- small 0.5 CPU / 2Gi, medium 1 / 4Gi, large 2 / 8Gi
- Storage
- 10Gi by default, chosen once
- Edition
- Community
- Public port
- Bolt (7687) can be opened on a public cluster
- Pause
- No; pause the project instead
03Binding
What your app receives
Bind it to an app and these arrive as environment variables. The values are generated once into a secret and reach the app from there, rather than as something you copy.
- NEO4J_HOST
- NEO4J_PORT
- NEO4J_HTTP_PORT
- NEO4J_USERNAME
- NEO4J_PASSWORD
- NEO4J_URI
04Adding it
Add Neo4j to a project
The same four steps as every service in the catalog.
- 01Open a project and go to Services.
- 02Pick it from the catalog and choose its options. Only the size is required; everything else has a default.
- 03Create it. Anyport installs it into the project's namespace, generates its credentials into a secret there, and tracks its health.
- 04Bind it to an app. The connection details arrive as environment variables, and rotating the credential never means editing an app.