Database Reference
In-Depth Information
system. For more info, see the “Securing access to the Neo4j Server” section in the Neo4j
11.4.2. Monitoring
Being able to monitor the health of your Neo4j system and understand when it's getting
into trouble is a good way to ensure a stable and long-running system. Most of Neo4j's
monitoring features are only available in the Enterprise edition of Neo4j, and they're
generally exposed through the Java Management Extensions (JMX) technology (
ht-
More information on what is available, and how to get hold of this information, can be
foundinthe
“
Monitoring
”chapter(chapter26)oftheNeo4jManual:
http://docs.neo4j.org/
11.5. Summary
Congratulations! You've reached the end of your Neo4j journey through this topic. In this
final chapter, you took a tour through the high-level Neo4j architecture, periodically dip-
ping beneath the covers, gaining some valuable insight into some of the will and whys of
certain Neo4j internals, especially in the context of configuring Neo4j to operate optimally
for a production environment.
Specifically, you gained insight into the factors required to calculate rough disk usage and
memory requirements for your Neo4j system. You also learned about Neo4j's two-tiered
caching strategy involving the filesystem cache and object cache, and how these can be
configured to suit your needs.
As this was the last chapter in the topic, we recapped some of the basic concepts you en-
countered in the previous chapters in the topic. With a solid understanding of the basic
Neo4j architecture, your final task involved learning how to perform the key tasks of con-
figuring Neo4j to run in a clustered High Availability setup, and also how to back up and
recover the database.
