ArangoGraph (Managed Service)
ArangoDBExternal reviews
115 reviews
from
External reviews are not included in the AWS star rating for the product.
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.
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.
Very performant free graph DB
What do you like best about the product?
Very professional graph DB designed from the ground up for multi model support, scaling (e.g., clustering and sharding built in), free open source and enterprise model but even free version has great community and official support.
Very good driver support, Java driver has become really advanced now with async support and direct access to VelicyPack serialization format.
Very good driver support, Java driver has become really advanced now with async support and direct access to VelicyPack serialization format.
What do you dislike about the product?
Proprietary query language AQL, no support for Apache Tinkerbob
Web UI still only has quite basic navigation, visualisation and query assistance (intelligent auto completion)
Web UI still only has quite basic navigation, visualisation and query assistance (intelligent auto completion)
What problems is the product solving and how is that benefiting you?
Using it for our generic sequencing platform, from user and UI level simple configuration storage to storing massive amounts of variant and sample data.
Recommendations to others considering the product:
Didn't check out 3.3 yet, Linux support is great. Watch out for resource usage, now with new RocksDB storage engine much easier on the system resources.
ArangoDB the multi-model Database
What do you like best about the product?
Different data models in the same database: Graph DB, Document Store and Key-Value Store with a single language for queries. With Foxx you can create HTTP microservices running inside the database.
What do you dislike about the product?
Nothing for now. Maybe need more community activities in different countries.
What problems is the product solving and how is that benefiting you?
To serve JSON documents and key-value objects in a single database core with a great performance and single language to manage them.
Recommendations to others considering the product:
Try it!!!
A single database for all my use-cases
What do you like best about the product?
The database allows you to the ability to literally serve any of your use-case and replace any of your current databases. It can act like a schema-less document store or as a graph database, that too without giving up on RDBMS features like Joins.
The query language AQL is especially very powerful.
Besides, the community is great and helpful!
The query language AQL is especially very powerful.
Besides, the community is great and helpful!
What do you dislike about the product?
Not anything specific actually, it is actually great.
The performance of RocksDB storage engine is comparatively lower than the standard mmfiles; But that TBH is not a reasonable thing to expect and would be like comparing apples to oranges because that performance is gained at the cost of resources.
The performance of RocksDB storage engine is comparatively lower than the standard mmfiles; But that TBH is not a reasonable thing to expect and would be like comparing apples to oranges because that performance is gained at the cost of resources.
What problems is the product solving and how is that benefiting you?
We were able to retrieve data quickly, give a search feature and show graphs in our applications - efficiently all using a single database i.e. ArangoDB!
Also, my benchmarking against Neo4j showed results very much in favour of ArangoDB (hence our application served much faster).
Also, my benchmarking against Neo4j showed results very much in favour of ArangoDB (hence our application served much faster).
Multi-purpose "NoSQL" database of my choice
What do you like best about the product?
ArangoDB provides a robust and feature-rich database implementation when you need a document store combined with a graph database. The ability to store documents and model arbitrary relations between documents using a graph is a key feature and often needed when your data model is not only flat or hierarchical but just connected in many different way. The query language AQL allows us to write queries similar to SQL. This is a major advantages over databases mis-using JSON as query language.
Transactional integrity, ACID compliance are also a big plus.
Transactional integrity, ACID compliance are also a big plus.
What do you dislike about the product?
Not many issues with the current Arango 3 release. Older release had various issues like non-persistence of indexes but the ArangoDB team addressed most issues in the latest releases which where blocking development and production.
What problems is the product solving and how is that benefiting you?
ArangoDB is a multi-purpose database for most of your business cases like content-management, arbitrary web applications. It is in many a serious alternative to Postgres.
Recommendations to others considering the product:
ArangoDB is absolutely worth a try. Of course there are often more specialized databases serving a particular usecase like time-series data etc. I value and promote ArangoDB because it solves a lot of problems with a clear design in mind and particular because the ArangoDB team knows exactly what they are doing. There is not much marketing buzz involved in ArangoDB and the personal and warm relationship with the ArangoDB team make me feel very comfortable when working on database-driven projects.
efficient graph traversal and relationship identification
What do you like best about the product?
Clear query structure which allows to execute efficient queries and sub-queries. The fact that the DB is schemaless makes us to redefine the data model effortlessly to incorporate more features to the collection as part of agile development. AQL allows to combine multiple functionalities within a single query resembling like a function in programming language which gives superior power over db operations
What do you dislike about the product?
As DB is schemaless retrieving attribute which does not exist throws null value instead of error which needs to checked appropriately.
What problems is the product solving and how is that benefiting you?
I am using ArangoDB for the purpose of identifying relationships between users based on their content consumption and underlying structure in the products (news, media content etc.,). The DB allows to quickly process relation computation queries so that latency between user request and recommendation considerably reduced.
Recommendations to others considering the product:
Fellas, ArangoDB has some of the unlocked potential in the world of graph databases although i cant comment in the document DB in which i haven't worked much. It supports complex computations and choice of storage engine suited to process big data. And moreover, support from the DB team and community was overwhelming and issues raised in github was seriously looked upon.
showing 41 - 50