Neo4j Production Ready: Enterprise Cloud

The cloud today has become the primary deployment option for startups and is gaining adoption across the worlds largest enterprises. As with other critical infrastructure holding sensitive organization or customer data, there are several key questions enterprises must consider when evaluating the Neo4j graph database cloud deployments.

When running Neo4j in production, especially for an enterprise, the obvious baseline is to use the Neo4j Enterprise edition because it offers high availability clustering, cache sharding, hot backup, enhanced monitoring, and a several other critical production features. Taking a shortcut here will leave your enterprise vulnerable to outages, data loss and little ability to upgrade as new versions of Neo4j are released.

Essential Neo4j Enterprise Database Features

In addition to the high availability clustering and hot backups a few of the key benefits of Neo4j Enterprise include:

• Enterprise Lock Manager
  The enterprise lock manager enables high levels of concurrency through fast lock resolution, which provides vertical scaling of concurrent applications beyond 5 CPU cores.
• Cache Sharding
  For large graphs this is very useful when paired with sticky sessions because it provides a high cache hit ratio where reads that are relevant to each instance in the cluster will warm the cache without needing to load the whole graph into memory.
• Property Existence Constraints
  This allows to specify a property that must exist on a node when that node has a certain label. This database enforced schema eases data integration within an enterprise environment as well as increases developer productivity.

You’ll definitely want to take advantage of Neo4j Enterprise for commercial deployments where availability and scale are critical.

Essential Neo4j Enterprise Cloud Features

While Neo4j Enterprise provides a robust foundation as a core database, there are a several additional operational concerns to address for an enterprise to go into production with a Neo4j cloud deployment.

• Security
  As with typical database deployments part of the security hardening process involves removing direct web access to the database through it’s accessible ports and protocols. Neo4j is no different. While Neo4j provides basic auth, it is not recommended to expose your Neo4j graph database production deployment with a publicly accessible URL.
  Public hosting options aren’t an option here. A Virtual Private

Read More......