ArangoGraph (Managed Service)
ArangoDBReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
115 reviews
from
External reviews are not included in the AWS star rating for the product.
Excellent database with very good graphics
What do you like best about the product?
I love the way you can easily use AQL queries, the documentation is comprehensive, also the software has a good default configuration, it also provides good facilities, it also allows to combine multiple functionalities within a single query that resembles a function in the language. programming, it also provides a robust and feature-rich database implementation, the ability to have a document store with junctions and graphics connections with cluster support is amazing, it also has excellent graphics features that allow it to be used as a single data source for a variety of client applications.
What do you dislike about the product?
I still don't have a bad experience with this product or anything that I might dislike about it, it offers me a large amount of very high quality data.
What problems is the product solving and how is that benefiting you?
It offers me the ability to manage all our infrastructure and resources in the cloud, it is very easy to understand the concepts of this database, I use it as the main data warehouse for all my data, it is very easy to start a new project using this database of data, it also allows to link many sources of information in a network, it is a very productive platform for all of us.
Recommendations to others considering the product:
You can start using it without any problem, it is a very easy to use tool that will be very useful in many aspects, I can assure you, I recommend that you start using ArangoDB.
Excellent graph database
What do you like best about the product?
1. It' easy to install both a single ArangoDB instance and ArangoDB cluster cross different OS, including CentOS, Ubuntu, MacOS and Windows. You could try and test graph database just through several steps.
2. The AQL is easy to learn and understand. The official document about AQL is very detailed. Everyone could learn it just by reading the AQL document.
3. The most important thing is that the AQL for graph traversal is very efficient. For a graph consisting of one hundred thousand nodes, it takes half an hour to query all rings which includes 6 to 12 nodes.
4. ArangoDB is schema free for a big graph. So it's easy to modify the graph structure without considering different problems.
5. ArangoDB support different cluster modes. That means however big your data is ArangoDB could dynamically scale out or in.
2. The AQL is easy to learn and understand. The official document about AQL is very detailed. Everyone could learn it just by reading the AQL document.
3. The most important thing is that the AQL for graph traversal is very efficient. For a graph consisting of one hundred thousand nodes, it takes half an hour to query all rings which includes 6 to 12 nodes.
4. ArangoDB is schema free for a big graph. So it's easy to modify the graph structure without considering different problems.
5. ArangoDB support different cluster modes. That means however big your data is ArangoDB could dynamically scale out or in.
What do you dislike about the product?
1. The graph display is not as clear as Neo4j. Although the GUI is not so important for a programer, it's a big problem for general customers because a beautiful and clear GUI could be more understandable for them.
2. ArangoDB could consider supporting Cypher. Cypher is easier to understand and many people have learnt it so maybe they don't like to learn so many different query languages.
2. ArangoDB could consider supporting Cypher. Cypher is easier to understand and many people have learnt it so maybe they don't like to learn so many different query languages.
What problems is the product solving and how is that benefiting you?
I use ArangoDB for the vehicle insurance fraud scenario. In that scenario, a group of fraudsters work together to make fake car accidents and claim body injuries and car damages. If we just check or use traditional statistical method to inspect a single car accident, a series of car accidents look normal and independently. It is very hard to recognize the fraudsters by machine learning methods because the fraud sample is rare and it's hard to label different group of fraudsters. However, we modeled all the cases via a graph. Specifically, the claim cases are modeled as nodes and first drivers, third-party drivers, passengers etc are also modeled as nodes. All persons are connected by claim case node via relationship edges. Then we search lots of abnormal rings which is capable of revealing relationship between persons who are acting like perfect strangers.
ArangoDB is so excellent to store and query a graph.
ArangoDB is so excellent to store and query a graph.
Power packed, easy, no learning curve !
What do you like best about the product?
This db is a power house of all no sql possibilities. With an active forum and slack channels, the support provided (even for community users) is great. We had used Neo4j before but it limits a lot of things for its enterprise edition and hence we moved on to Arango and we are indeed happy.
What do you dislike about the product?
The docs are incomplete at a few places. Initially it was a bit difficult to find answers, but the Slack groups were super helpful.
What problems is the product solving and how is that benefiting you?
We have a many to many relationship data analysis problem. After trying SQL (postgres) and Neo4j, we moved to ArangoDB and since then we are happy.
Recommendations to others considering the product:
Just go for it. It has really good support and the ease of usage will blow your mind.
So Rich and Well Put Together
What do you like best about the product?
Migrating a project to ArangoDB from a document DB was intimidating at first but with all the tools it comes packing made it much easier. The query language has a pretty shallow learning curve while at the same time equipping you with so much power.
The rich web interface was the most useful for me; it allowed me to play around with data and queries before committing anything to actual implementation.
The rich web interface was the most useful for me; it allowed me to play around with data and queries before committing anything to actual implementation.
What do you dislike about the product?
I've had no complaints so far, but I'll be sure to raise if I have any
What problems is the product solving and how is that benefiting you?
Enforcing integrity and consistency of stored data was becoming tedious with increasing complexity. ArangoDB took away all the checks and rules that had to be hardcoded in the application
Recommendations to others considering the product:
Coming from a document DB, ArangoDB is quite easy. Only some minor refactoring required to be up and running, then you can proceed to implement the other features
A cool (AQL) document DB
What do you like best about the product?
I am currently using ArangoDB on my Python project, via python-arango. I am loving the way you can easily use AQL queries on your DB transactions, as well as managing your database and collections. You can also setup a highly available database or a main-failover setup, which can make your backend implementation better.
What do you dislike about the product?
I don't think I have a dislike on any ArangoDB features, since all or most of my usage are fluently fine.
What problems is the product solving and how is that benefiting you?
ArangoD handles all my document/transaction related concerns, and the performance doesn't impact any issues.
Recommendations to others considering the product:
If you're looking for a document DB with rich features, you should try and use ArangoDB.
Powerful, Flexible, Performant Database
What do you like best about the product?
The multi-model Document/Graph paradigm is a big draw, and good search performance & a very intuitive query language makes the database genuinely enjoyable to use. Documentation is good, and development/support pace is fast.
What do you dislike about the product?
Some search error messages can feel opaque, although errors should be rare.
What problems is the product solving and how is that benefiting you?
We're keeping track of complicated relationships between articles and entities that need to be kept updated to the minute. We're also looking at moving our RBAC systems to Arango as a natural fit for the graph-based structure.
Feature-rich graph database
What do you like best about the product?
1) Amazing feature-rich query language (AQL), subjectively much easier to use if compared to GraphQL
2) Pregel engine with major graph traversal algorithms available out-of-the-box - we were able to remove large piece of homebrew code with it
3) Nice performance at scale, both write and read
4) Inverted Index available in ArangeSearch - lighting fast!
5) Comprehensive admin UI
2) Pregel engine with major graph traversal algorithms available out-of-the-box - we were able to remove large piece of homebrew code with it
3) Nice performance at scale, both write and read
4) Inverted Index available in ArangeSearch - lighting fast!
5) Comprehensive admin UI
What do you dislike about the product?
1) Slow built-in graph visualization, it makes difficult to explore graphs from admin UI.
2) Need to re-write code when switching from single node to cluster node.
3) Slow analytical queries, e.g. aggregations for entire collection. However it's not the primary case for multi-model databases at all.
2) Need to re-write code when switching from single node to cluster node.
3) Slow analytical queries, e.g. aggregations for entire collection. However it's not the primary case for multi-model databases at all.
What problems is the product solving and how is that benefiting you?
We're using ArangoDB as our engine for Identity Graph - huge graph connecting users and devices in deterministic and stochastic way.
Major benefit is finally having native graph database working as intended at scale.
Major benefit is finally having native graph database working as intended at scale.
Recommendations to others considering the product:
If you're using several NoSQL databases it means you probably need multi-model database. Give ArangoDB a try - it's very balanced product in this sense.
If you're looking specifically for graph database with complex queries - most probably you don't have to much candidates in principle. ArangoDB is first-class citizen in this space.
If you're looking specifically for graph database with complex queries - most probably you don't have to much candidates in principle. ArangoDB is first-class citizen in this space.
Amazingly good!
What do you like best about the product?
So many software companies have a “good produce” but have huge gaps somewhere - poor support, steep learning curve, extraordinarily high pricing, ridiculous development base (“Jython”, I’m looking at you!), etc.
ArangoDB is the first product I have used (in 20 years!) that is complete. It is developer-friendly, user-friendly, has amazingly good support, is extremely performant, plays nice in cloud-native land, has built-in clustering, and (last, but NOT least) IT WORKS!
I am continually amazed at how often I am PLEASENTLY surprised by features, performance, or the company.
ArangoDB is the first product I have used (in 20 years!) that is complete. It is developer-friendly, user-friendly, has amazingly good support, is extremely performant, plays nice in cloud-native land, has built-in clustering, and (last, but NOT least) IT WORKS!
I am continually amazed at how often I am PLEASENTLY surprised by features, performance, or the company.
What do you dislike about the product?
Honestly, there isn’t much to NOT like. The only complaint I’ve had so far is that I had to change my query style to be able to fully utilize clustering. This meant learning, but it works.
What problems is the product solving and how is that benefiting you?
We are building a system that links many databases together to enable IT operations from configuration management to automation to financial reporting. Think “BaceFook for computers.”
Document storage allows us to be flexible in development while the graph powers new insight and allows us to link many sources of information into a web of knowledge (as opposed to a quagmire of misery).
Document storage allows us to be flexible in development while the graph powers new insight and allows us to link many sources of information into a web of knowledge (as opposed to a quagmire of misery).
Easy to learn, quick, but young
What do you like best about the product?
Graph database, AQL which is SQL friendly and KV storage + Document storage + Graph storage in only one solution
What do you dislike about the product?
Setup production cluster outside (DC/OS) is not easy
What problems is the product solving and how is that benefiting you?
Find the shorter path between two nodes, keep only one database engine for all needs (lower administration cost)
Great features and support
What do you like best about the product?
The ability to have a document store with joins and graph connections with cluster support is amazing. The Foxx framework makes a very convenient way to embed logic into the database and provide a clean interface for any REST interface. Web interface is really nice.
What do you dislike about the product?
Often find queries that are really slow - but usually just an index issue.
What problems is the product solving and how is that benefiting you?
Currently as doc store. RocksDB makes it easy to have larger-than-memory datasets.
showing 71 - 80