The Neo4j Operations Manual v4.4

© 2022 Neo4j, Inc.

Documentation license: Creative Commons 4.0

This is the operations manual for Neo4j version 4.4, authored by the Neo4j Team.

This manual covers the following areas:

  • Introduction — Introduction of Neo4j Community and Enterprise Editions.

  • Installation — Instructions on how to install Neo4j in different deployment contexts.

  • Cloud deployments — Information on how to deploy Neo4j on cloud platforms.

  • Docker — Instructions on how to use Neo4j on Docker.

  • Kubernetes — Instructions on how to use Neo4j on Kuberenetes.

  • Configuration — Instructions on how to configure certain parts of Neo4j.

  • Manage databases — Instructions on how to manage multiple active databases with Neo4j.

  • Clustering — Comprehensive descriptions of Neo4j Causal Clustering.

  • Fabric — Instructions on how to configure and use Neo4j Fabric.

  • Backup and restore — Instructions on how to back up and restore Neo4j deployments.

  • Authentication and authorization — Instructions on user management and role-based access control.

  • Security — Instructions on server security.

  • Monitoring — Instructions on setting up Neo4j monitoring.

  • Performance — Instructions on how to go about performance tuning for Neo4j.

  • Tools — Description of Neo4j tools.

  • Reference — Listings of all Neo4j configuration parameters.

  • Tutorials — Step-by-step instructions on various scenarios for setting up Neo4j.

  • Advanced Causal Clustering — Advanced concepts and actions for Neo4j Causal Clustering.

  • Deprecated security procedures — Deprecated security procedures.

  • Query routing decisions — Query routing decisions.

For information on upgrading and migrating Neo4j, see Neo4j Upgrade and Migration Guide.

Who should read this?

This manual is written for:

  • the engineer performing the Neo4j production deployment.

  • the operations engineer supporting and maintaining the Neo4j production database.

  • the enterprise architect investigating database options.

  • the infrastructure architect planning the Neo4j production deployment.