The 5-Minute Interview: Native Graph Storage and Connected Data - DZone Database

“When we first started exploring Neo4j’s native graph database, we saw benefits in how the data was stored because it paralleled real-world connected data,” said Benjamin Nussbaum[1], Co-Founder at GraphGrid[2].

He and his team realized that the future of data was connected data, and this needed to be reflected in the data architecture of their product in order for customers to use their data most effectively.

In this week’s five-minute interview (conducted at GraphConnect San Francisco[3]), we discuss how GraphGrid uses the benefits of native graph storage to provide a truly scalable product to customers.

Q: Talk to us about how Neo4j is related to GraphGrid.

Benjamin Nussbaum: GraphGrid is an enterprise data platform built around Neo4j[4], which we’ve been working with for about five years.

At its core with graph ops, it provides all of the orchestration management for scaling out Neo4j starting from a single instance in a single region all the way out to a cluster in that region. It even has the flexibility to span multiple availability zones within that region and scale that cluster to multiple regions.

This means you could go from Oregon to Virginia to Ireland, Frankfurt, and Sydney until you reached the full global scale of Neo4j. GraphGrid also provides the flexibility to change your core instance properties, such as if you need to go from 4 GB of memory to 8 GB to 16 GB to 32 GB, you can do all of that with zero downtime. Or if you need to upgrade from Neo4j 3.0 to 3.2, you can do that with zero interruption or downtime as well.

Q: What made you choose Neo4j?

Nussbaum: We were running into a number of challenges with the typical relational database[5] in terms of getting it to scale for the problems we were asked to solve.

When we first started exploring databases optimized for connected data, including Neo4j’s native graph database[6], we saw benefits in how the data was stored because it paralleled real-world connected data. This needed to be reflected in our data storage if we wanted to use our data most effectively.

Because Neo4j is a native graph database and treats relationships as first-class entities, we have a tremendous advantage when building connected enterprise solutions, building 360 customer reviews or connecting an enterprise with master data management[7]. In all of these cases you need to bring the data together in its connected state, and understand how it’s connected.

We realized early on that the future is connected data[8], and today we have a strong engineering team building connected data solutions.

Q: What are some of the most interesting or surprising ways you’ve seen your customers use Neo4j?

Nussbaum: Some of the most interesting ways our customers have used GraphGrid has been on the graph analytics side, using it to orchestrate a distributed graph-compute framework. With the orchestration to scale up and scale out, you can go from having your core Neo4j cluster of three instances, which is where your applications are interacting in real time, but you also need ad hoc analytics.

You can create another grid — which is just a logical grouping of instances — and say, “This is my analytics grid, and these instances need to be ten times bigger.” Keep in mind that a grid controls the region where your instances are deployed, as well as the instance type, the IOPS, and all of the attributes of those instances.

With all of that, you have very efficient control to develop a set of instances that are ten times bigger, run all of the ad hoc analytics and scale out the grid to 40 instances to perform temporary heavy offline compute, and then bring it back down — all without impacting your core cluster that is servicing real-time requests for your application.

Q: Is there anything else you’d like to share?

Nussbaum: The focus of GraphGrid in 2017 is validating our new self-service dashboard. So far we have a fully managed service with Neo4j, and the dashboard will put a lot of the flexibility of managing operations into the hands of our customers, which will be a huge benefit.

As we see an increase in the adoption of Neo4j, we see a challenge for customers in the operational component from startups to enterprise. Our experience running Neo4j in production has led us to build into the GraphGrid platform the foundation for any company to get up and running with Neo4j very quickly, especially if they’re on AWS[9].

We also want to provide a way to bring the community together in terms of deploying and running the different plugins, extensions and APOC procedures to provide an efficient way to get up and running, as well as to accelerate the adoption of graph database[10] technology.

References

  1. ^ Benjamin Nussbaum (twitter.com)
  2. ^ GraphGrid (www.graphgrid.com)
  3. ^ GraphConnect San Francisco (graphconnect.com)
  4. ^ Neo4j (neo4j.com)
  5. ^ relational database (neo4j.com)
  6. ^ native graph database (neo4j.com)
  7. ^ master data management (neo4j.com)
  8. ^ the future is connected data (neo4j.com)
  9. ^ especially if they’re on AWS (neo4j.com)
  10. ^ graph database (neo4j.com)

Comments

Post a Comment

Popular posts from this blog

New Article Posted: Seven Things You Should Do in Your AMS

Given how advanced and thorough the modern association management software (AMS) system has become, there are many opportunities for your organization to leverage it. Here are seven ways I believe every association should be using their AMS. Click here to read the rest of the article . Of course, if you’re already on my  announcements list , you would have received notice of this new article right in your email box. Not signed up yet?  Click here to sign up . Go to the article
Read more

10 Common Mistakes Biblical Counselors Sometimes Make, Part 8

Image
A Word from Bob: You’re reading Part 8 of a 10-part blog series on 10 Common Mistakes Biblical Counselors Sometimes Make . Mistake #1: We Elevate Data Collection Above Soul Connection . Mistake #2: We Share God’s Eternal Story Before We Listen Well and Wisely to Our Friend’s Earthly Story . Mistake #3: We Talk at Counselees Rather Than Exploring Scriptures with Counselees . Mistake #4: We Practice Half-Biblical Counseling If We Address Sin but Neglect Suffering . Mistake #5: We Fail to Follow the Trinity’s Model of Comforting Care . Mistake #6: We Tend to View People One-Dimensionally . Mistake #7: We Devalue Emotions Rather Than Seeing Emotions as God’s Idea . Mistake #8: We Minimize the Complexity of the Soul-Body Interconnection Because we are soul physicians and soul care-givers, our tendency is to focus on matters of the soul. Most biblical counselors are not trained in the medical field, so we wisely avoid offering medical guidance. Yet, that appropr
Read more