In this section, we are going to address a third and alternative way of getting started with the Neo4j graph database management system--using a cloud solution. As it turns out, you can try out the power of the database solution without even having to go through the previously mentioned steps of installing the product on an operating system of your own. You can just use a graph as a service solution; there are multiple providers out there. At the time of writing this, you can use solutions from the following:
GrapheneDB
Heroku
GraphStory
GraphGrid
Azure
A roll your own solution on CleverCloud, OVH, Google Cloud Platform, OpenShift, Amazon Web Services (AWS), and so on, is possible as well
Consider a hosting provider allowing you to use Docker, so you may roll your own image. More details on Docker installation later in this chapter.
Therefore, we are going to explain and illustrate some of the principles of a cloud-based deployment model and how you can use it to get started. To do so, we will be using the GrapheneDB platform--probably one of the most simple, elegant, and powerful solutions out there.
Getting started with the cloud platform consists of a few simple steps:
Register with GrapheneDB. This is easy enough, as they offer a free tier (depends on the hosting region) to test out the solution and get started:
Starting with GrapheneDB
Create a database instance. This is the equivalent of starting up a Neo4j server, but not on your own server hardware:
Create a new database 1/2
Create a new database 2/2
Once the database has been created, we are advised to create a user:
Create a new Neo4j user 1/2
For the limited use of our Sandbox, our new user will not expire:
Create a new Neo4j user 2/2
Start using a Neo4j database
After validating, go in the Overview tab. Click on the Launch button in the Tools section.
In this browser interface, we can do everything we would normally be able to do, except for the fact that this interface is protected by an implicit username/password combination. Running a few queries immediately feels familiar; the experience is nearly identical to that of running a local database server:
Accessing the Neo4j browser
One of the few differences that you will notice is the way you access the REST interface, for example, if you are using specific language bindings. These configurations are very specific and need to be taken into account.
Finally, if you want to administer your cloud-based Neo4j system, you can access the following web page to, say, perform exports and imports of your database. The latter is of course interesting and important, as it allows you to create a database on your local machine and then transfer the zipped graph.db directory to the Neo4j instance at http://www.graphenedb.com/ (under the Admin tab, look for the Export database button).
I hope this gives you a good overview of how you can get started with Neo4j with a provider such as GrapheneDB. It definitely flattens the learning curve even further and makes it easier for people to start using Neo4j in real production environments.