ArangoGraph (Managed Service)

My main use case for ArangoGraph is to build a customer graph in order to create a relation between customer and end users. I connect all the user related data together between the orders that they made from the supplier and customers.

The user interface is the best feature that ArangoGraph offers. The simplicity of the user interface is very appealing to me. ArangoGraph has positively impacted my organization as we made a 30% saving in order to build this graph. The savings were achieved mostly through time cost.

I think that ArangoGraph can be improved.

I have been using ArangoGraph for six months.

I advise others looking into using ArangoGraph to speed up the development using all the features that the product provides. I gave this review a rating of 8.

Public Cloud

Amazon Web Services (AWS)

What do you like best about the product?

Arango DB offers a great deal of flexibility. Its query language is straightforward and easy to grasp, making it accessible even for those new to the system. The performance remains strong, even when handling complex relationships, which adds to its appeal. Overall, I find it to be a very versatile database solution.

What do you dislike about the product?

The learning curve can be a bit steep at first, especially when you are building a new database.

What problems is the product solving and how is that benefiting you?

ArangoDB has helped me develop more quickly and maintain a simpler architecture. Overall, it saves time and reduces infrastructure overhead.

What do you like best about the product?

The everything about it is the best everything is best

What do you dislike about the product?

Nothing to dislike about arango DB you cannot dislike it

What problems is the product solving and how is that benefiting you?

ArangoDB is a multi-model database, which means it supports document, graph, and key-value data models in a single engine. Because of that, it solves several common database problems that developers usually face when using multiple separate databases

What do you like best about the product?

It lets you work with documents, graphs, and key-value pairs in one engine, without needing separate databases or complex integrations. This flexibility simplifies architecture and boosts performance for applications that require mixed data models. The built-in query language, AQL, is also powerful and intuitive, making complex queries feel clean and readable.

What do you dislike about the product?

Learning curve can be steep for newcomers

What problems is the product solving and how is that benefiting you?

ArangoDB solves the problem of needing multiple databases for different data models.

What do you like best about the product?

Unique ane multiple model database where everything is access using just one query.

User interface is pretty good and it makes it very easy to navigate and analyse also debugging if any issues.

AQL is soo quick to learn and leads Arango to be convenient platform.

What do you dislike about the product?

Support team needs to be little more proactive. They are doing a great job but prompt replies are missing.

What problems is the product solving and how is that benefiting you?

Multi model support of Arango db allowed me to integrate multiple data models in a single query. It is great suited for complez requirements.

What do you like best about the product?

Seamlessly handles graph, document, and key-value data in one powerful engine

What do you dislike about the product?

Steep learning curve and limited community support for complex queries

What problems is the product solving and how is that benefiting you?

ArangoDB solves the challenge of managing multiple data models separately by combining graph, document, and key-value storage in one system. This flexibility saves time, reduces infrastructure complexity, and allows me to design more efficient and scalable applications without juggling multiple databases.

What do you like best about the product?

It was simple to setup and was easy to understand. Now whenever we got some issue, the customer support was always their to tackle the issue. Now after the setup of arrango the frequent use of it between developer has increase and because of the its wide range of features we could integrate it easily.

What do you dislike about the product?

There were not such dislikes but somewhere accessing the data was not an cakewalk.

What problems is the product solving and how is that benefiting you?

A single place to store all the data

What do you like best about the product?

The compatibility between the looseness of schema-less design and the flexibility as a graph database is excellent.
The ability to write JSON-first queries using AQL.
Conveniently includes a rich Web UI.
It is equipped with a full-text search engine that is relatively easy to use.

What do you dislike about the product?

It seems unavoidable due to performance reasons, but management and operations on collections and databases using AQL are weak.
If there were more capabilities for operations on collections and databases, the possibilities would expand.

What problems is the product solving and how is that benefiting you?

It is used to support designs where the elements to be managed have dynamically variable attributes and require numerous relationships.
By leveraging the strengths of document databases and graph databases, it addresses issues such as the lack of a fixed schema and complex relationships, which could become bottlenecks in conventional databases.

What do you like best about the product?

Arango DB was suggested to me by my seniour as it's open source and provide a great platform for graph databases, It was very user friendly for a graph database, it was very easy to create vetices for the graph visuallise them in my local container and there after making edge definition and connecting them saved me so much time for initial POC with graph RAG.

What do you dislike about the product?

Documentation for the DB can be better with a section of website dedicated only Documentation in details i found myself going website to website finding the things i needed for my use case other than that it was really good.

What problems is the product solving and how is that benefiting you?

Being an Open Source DB it's solving the problem of not being expensive for starters there after it's beginer freindly implementation can be learned by freashers and can easily be incorporated to prodution grade systems. Being in an early stage startup it helped me to do my initial POC very fast and helped me with my research on Graph RAG

What do you like best about the product?

It is simple. Much better than Mongo. Treating edges as collection, I believe a mster stroke. Enables both graph and document DB at a time

What do you dislike about the product?

Nothing at time point. Probabaly not yet being comoatiable Gremilian?

What problems is the product solving and how is that benefiting you?

We have a situation where the meta-data about our solution has complex relationships. At each node, the data needs to be schemaless. We also may need to do traverse the graphs in multiple complex ways. And, do so quickly and have the ability to hos this data platform within our cluster.