A free fortnightly newsletter on Taxonomy, Thesauri & Ontology and Semantic Publishing
Some points to consider before buying a graph database
Graph databases are witnessing an upsurge of interest from enterprises, primarily for their speed and user-friendliness. There are many graph databases, each with their own strengths. Some enterprises are testing and buying them. For others, Mingxi Wu, Vice-President of Engineering for TigerGraph, offers his suggestions. Mingxi bases his recommendations on the years of experience gained from working on real-world graph management problems and with TigerGraph, the world’s fastest graph analytics platform for enterprises.
When making a decision on which graph database (DB) to buy, an enterprise must take into account the development language it is going to use. In addition, there are different nuances among the database vendors for different use cases. Therefore, enterprises must scope this out ahead of time to make sure that the most effective language and DB is selected for the corporate purpose. Furthermore, an enterprise should go beyond discussing which graph language is the best or how a new unified option can be created. Instead, it should find the answer to a more fundamental question: What are the prerequisites for a graph query language in the first place?
Click here to read the recommendations in detail.