GrapheneDB Blog

Updates from the GrapheneDB team

Our New Add-on Helps Heroku Users Build Applications on Top of Neo4j

To build and run powerful apps on top of Neo4j databases, you need a reliable partner to keep those databases running. GrapheneDB’s hosting service for the Neo4j graph database is now available to Heroku users. We’ve launched a beta version of our add-on that’s public and immediately available for use.

Access the public Docs at the Heroku Dev Center.

More about the add-on

  • It includes all the features offered by GrapheneDB.
  • By default, the add-on will provision Neo4j 2.0 instances with support for labels, the new browser and more.
  • Support for Gremlin is available for Neo4j 1.9 (Gremlin is not included in 2.0 releases anymore)

Migration from Neo4j add-on

If you want to migrate from the Neo4j add-on, follow these simple steps at our Heroku docs page.

 Why Use Graphs?

Graph databases help you recognize and exploit relationships among your data that are otherwise difficult to manage. They’re built specifically to treat relationships as first-class citizens and scale with predictable query time regardless of the overall size of the data set.

 Get Started

GrapheneDB makes it easy to set up and maintain your neo4J databases, so you can focus on building a powerful app. Contact us and learn how to get a dedicated instance for your Heroku app up-and-running.

Maintenance Next Monday July 22th 18:00 CEST

Affects: All customers using sandbox databases.

  • When: 2013-07-22 18:00 CEST (Central European Time)
  • Duration: 20 minutes
  • Expected downtime: 10 minutes

No changes required.

Reason: We are going to deploy new software on to the servers hosting the sandbox databases. A system reboot is required.

Additional details: No action is required by users. Current configuration will work as usual.

Maintenance Next Thursday June 20th 14:00-15:00 CEST

There will be a maintenance window next thursday 14:00-15:00 CEST (Berlin time). The actual downtime should be just around 10 minutes within that time frame.

We will migrate all sandbox databases to a new dedicated server hosted on SoftLayer. This migration should not have any negative impact on the performance or availability.

As usual, if you run into any issues or if you have any questions please get in touch with us at support@graphenedb.com.

Maintenance 17:00-18:00 CEST. Introducing Support for Neo4j 1.9 & 2.0

There will be maintenance window today at 17:00-18:00 CEST (Berlin time) today while we deploy the latest changes in our backend.

This is some of the new things you can expect:

Unique domains

Sandbox databases are getting unique domains, to avoid issues with stored authentication credentials on certain browsers.

You should update the connection settings of your app, although we will ensure compatibility with the old settings for a week.

Running Neo4j Community Edition 1.9.RC2 and 2.0.0-M02

Until now we have just been offering to run Community Edition 1.8.2 stable, but some of you have asked for support of other versions. Perhaps you can be interested in trying or benchmarking your app with different versions of Neo4j.

From today on we are introducing versions 1.9.RC2 (release candidate) and 2.0.0-M02 (developer preview), besides 1.8.2 stable.

As usual, if you run into any issues or if you have any questions please get in touch with us at support@graphenedb.com.

April News: Updates From the Last Few Weeks

Berlin & Graph DB meetup

I did a short trip to Berlin last month. During that trip I also attended a graph DB meetup where I gave a talk about polyglot persistence with Neo4j.

I’d like to thank Michael Hunger, Stefan Plantikow, Peter Neubauer and Pernilla Lindh for organizing the event, being a great host and most of all for the great conversation.

New features

This is a summary of the latest features that we have released.

Restore

We have introduced the restore feature around a month ago. You can do a DB restore using a zipped Neo4j DB file. This way, you can easily dump the contents of the DB on your local machine or a sample data set and take to your DB hosted on GrapheneDB,.

We will add support to export your DB using the same format in the next weeks.

Improved compatibility with drivers

We have a test suite to ensure that popular languages and drivers work seamlessly with GrapheneDB.

We have added a few new drivers to that test suite and also included configuration snippets for them in the dashboard. This doesn’t mean that other drivers won’t work, it’s just a list of drivers that we use to test against to make sure everything works fine.

For a complete list of our tested drivers please visit our FAQ section.

Vanilla Neo4j

One of the reasons that we have been very busy lately and also the most important feature is that we have migrated our architecture to host vanilla Neo4j instances rather than a wrapper around Neo4j.

This means you can expect the same features from GrapheneDB as you get from Neo4j Community Edition. We explicitely don’t support Gremlin and REST API Traversals because they rely on Groovy, and that could cause security issues on our shared machines for the sandbox plans. At the moment we are running Neo4j v1.8.2, but we also plan to allow other versions in the future.

Support for indexes

Index support has ben on our to do list for a while. As a nice side effect of the migration to vanilla Neo4j indexes are now fully supported.

NoSQL matters this week

I’m attending NoSQL matters in Cologne today and tomorrow. Feel free to ping me on twitter or mail me at alberto at graphenedb dot com if you want to talk.

Maintenance Window Today 7pm-8pm CEST

There will be maintenance window at 19:00-20:00 CEST (Berlin time) today while we deploy the new architecture and migrate all existing databases to the new sandbox plans running Neo4j 1.8.2.

What this means for you

  • As part of this change in the architecture and the DB instances the URLs to access your databases Neo4j REST API will change. After the migration you will need to login and get your new connection settings.
  • Your existing DB will be migrated without data loss to our new sandbox plans running vanilla Neo4j.
  • All new databases will be setup as vanilla Neo4j instances.
  • You can expect all features that you can get from Neo4j community edition, v 1.8.2. excluding: REST API Traversals and Gremlin. It’s worth mentioning that Cypher is a great replacement for both and fully supported.
  • You will have access to Neo4j Web Admin interface. You will find a link to it in your database dashboard after the migration is concluded.
  • Support of Neo4j REST drivers has been improved. Any driver compatible with Neo4j 1.8.2 Community Edition should work as well with GrapheneDB. If you do find an issue just let us know and we will fix it ASAP.

Documentation and support

We are in the process of updating our website and the developer docs to reflect this change. Please be patient if you can’t see the whole content yet.

As usual, if you run into any issues or if you have any questions please get in touch with us at support@graphenedb.com.

Introducing Our Blog

Hello World!

This is our first post on this blog. We will be posting about new features, events, demo applications, etc.