Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
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
- Leave a Comment |
- Mark review as helpful
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.
Excellent compromise between flexible structure and RDBMS capacities
What do you like best about the product?
The semi-structured and very extensible document model, combined to most of the assets of a hard RDBMS : indexes, joins… plus a few interesting capacities : fulltext indexation, cluster mode. Also, the very active and helpful developers team.
What do you dislike about the product?
Sometimes it feels like some features are still lacking or don't give their full potential yet, but the product is constantly evolving and new features appear every month.
What problems is the product solving and how is that benefiting you?
Our use case is scientific (non-comercial) statistical exploitation of crowdsourced data. Previously using CouchDB, we ran into limitations due to disk space increasing exponentially, and difficulty to perform various complex queries in a reasonable time. ArangoDB allows all that by leveraging most of the powerful concepts of a RDBMS, while keeping a very convenient and extensible semi-sctructured documents orientation. It opens new perspectives for data-mining while keeping a very good read performance thanks to indexes.
Recommendations to others considering the product:
Cluster mode doesn't implement all functionalities yet, and is way slower (at least with community edition). While this is totally understandable, it might be disappointing if one expects it to be "magical scaling". The replication is not as good as CouchDB at the moment.
Good all purpose database with great promise
What do you like best about the product?
Ease of use, nice admin ui where you can test queries (and explain them) and play with arango, many driver options. Overall a good developer experience. It is under active development and there is a github/slack where the arango team responds to issues. AQL is simple and parallels SQL nicely while offering some of its own special things.
What do you dislike about the product?
Some small bugs and quirks. Have upgraded a few times to get bugfixes. I dislike that there are enterprise only features. (I guess you gotta make money somehow.) I also found that under heavy load I experienced seemingly random errors and that my applications could overload the database, locking it up. The java driver didnt have all the features I wanted, namely a connection health check. One pesky frustration is that when you google stuff from the documentation, the top result is often not the current version of the documentation, and then switching versions on the page brings you to the documentation home page.
What problems is the product solving and how is that benefiting you?
Multimodel is nice - arango can be used for different projects with different goals. Also taking advantage of their clustering for redundancy.
Good software, doc and community
What do you like best about the product?
Documentation, tooling, and more generally user experience are the best I had in a long time.
The software has a good default configuration, no bullshit, and it is based on well-tested building blocks.
The community and especially Arango's employee are always very responsible for all kinds of problems.
And of course, pretty decent performances and forgiveful to misuse of some features.
The software has a good default configuration, no bullshit, and it is based on well-tested building blocks.
The community and especially Arango's employee are always very responsible for all kinds of problems.
And of course, pretty decent performances and forgiveful to misuse of some features.
What do you dislike about the product?
Client API are not that good nor efficient. One would have expected a better C++ client than one based on Curl for instance.
Actually, it is so easy to start using and testing Arango that one can miss some important things in the documentation and gives a false impression of bugs/slowness sometime.
Actually, it is so easy to start using and testing Arango that one can miss some important things in the documentation and gives a false impression of bugs/slowness sometime.
What problems is the product solving and how is that benefiting you?
We try to represent a social graph and get out business value out of the links. Traversals, for instance, are something difficult to do efficiently and Arango seems to do a decent job.
Recommendations to others considering the product:
Work on your data model and understand relations.
showing 51 - 60