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.
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.
- Leave a Comment |
- Mark review as helpful
Worth testing
What do you like best about the product?
Graph analysis is very easy, the database helps a lot in connecting different entities rather than bringing them to Spark then try to find those connections, which gives a lot of flexibility and speed boost.
What do you dislike about the product?
No ANSI SQL support, I was hopping for SQL support, that was a disappointing thing to learn a new language. We use CQL at the moment, Spark SQL, and SQL on MySQL, now we have to adapt to AQL which is an unnecessary overhead in my opinion.
What problems is the product solving and how is that benefiting you?
Graph analysis, rather than Spark + Cassandra, yet still experimenting.
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!!!
An easy way to do complex things
What do you like best about the product?
Document and Graph database at the same time;
It's easy to query the database with AQL;
It's easy to query the database with AQL;
What do you dislike about the product?
Not a big issue, but I think database should keep the connection open like other databases.
What problems is the product solving and how is that benefiting you?
We create an Open Source application called Globomap with an ability to map all our infrastructure and cloud resources, and correlate with each other. So, we can find any resource, no matter the starting point.
Recommendations to others considering the product:
If you coming from another document database, just give it a try. The learning curve is minimal compared to other graph databases.
AQL will help you with complex queries.
AQL will help you with complex queries.
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).
Graphing and much more
What do you like best about the product?
Everything built in (clustering, graphs, web services)
What do you dislike about the product?
There is no ArangoDB as a service in the cloud
What problems is the product solving and how is that benefiting you?
Information management and visualization
ArangoDB enabled our business to grow
What do you like best about the product?
Everything. All just work!
Graph DB
Document Store
Key-Value Store
HTTP Rest Endpoints (and GraphQL)
AQL
Graph DB
Document Store
Key-Value Store
HTTP Rest Endpoints (and GraphQL)
AQL
What do you dislike about the product?
Javascript. My problem
Web UI is sometimes a little unresponsive but easily fixed.
Web UI is sometimes a little unresponsive but easily fixed.
What problems is the product solving and how is that benefiting you?
Graph, Document, Key Value and HTTP REST/GraphQL. In ONE Package?
Surely they can't all be good?
Performance? Yup. Removed Redis
Storage: Replaced Postgres
Graph: No real competitor (Neo4j runs on a JVM and uses Cypher which is a b s t r a c t)
Pregel Algorithms on Graph. Again, not easy to find a useful
REST Endpoints for data Access and CRUD actions. Foxx. and super fast!
And tying it all together is AQL. A wonderous, modern language that enables really impressive complicated queries and processes to be pushed to the backend. People say its good if you come from a SQL background. I hate SQL but I love programming and it really fits with that concept to me.
All of the above have enabled me to trust and rely on ArangoDB as THE technology to power a complex platform.
Surely they can't all be good?
Performance? Yup. Removed Redis
Storage: Replaced Postgres
Graph: No real competitor (Neo4j runs on a JVM and uses Cypher which is a b s t r a c t)
Pregel Algorithms on Graph. Again, not easy to find a useful
REST Endpoints for data Access and CRUD actions. Foxx. and super fast!
And tying it all together is AQL. A wonderous, modern language that enables really impressive complicated queries and processes to be pushed to the backend. People say its good if you come from a SQL background. I hate SQL but I love programming and it really fits with that concept to me.
All of the above have enabled me to trust and rely on ArangoDB as THE technology to power a complex platform.
Recommendations to others considering the product:
Do it. Learn it. Embrace it.
Never regretted our choice
What do you like best about the product?
AQL is rather easy to pick up and feels rather natural. The web interface is perfectly fine. The documentation is comprehensive and the community is absolutely friendly and helpful. It is backed up by a motivated company and the contact to the people over there has always been a pleasure.
The multi-model approach is great and enables us to fulfill the whole of our project needs with just one DB product.
The integration of Foxx Microservices directly into the DB is a nice topping. The balance between open source and enterprise features is at a sweet spot.
The multi-model approach is great and enables us to fulfill the whole of our project needs with just one DB product.
The integration of Foxx Microservices directly into the DB is a nice topping. The balance between open source and enterprise features is at a sweet spot.
What do you dislike about the product?
Honestly? There is nothing I dislike at this point.
What problems is the product solving and how is that benefiting you?
Performance! Even in comparison to other fast NoSQL DBs, Arango performs really nice while letting you do some query magic I would never want to miss again and feeling rock solid. We have it in production for somewhere around two years and never had any problems.
Recommendations to others considering the product:
Just give it a go. We fell in love.
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.
Zero to 60 App Development
What do you like best about the product?
ArangoDB's speed is nothing short of exceptional. Additionally, AQL has made my time spent creating queries be cut in half over other document or relational databases.
What do you dislike about the product?
I would like more documentation and support for clustering outside the realms of DC/OS and Mesos.
What problems is the product solving and how is that benefiting you?
We currently utilize ArangoDB for all new development involving hybrid mobile applications, and web applications.
Recommendations to others considering the product:
Please focus more on clustering on setups that do not include DC/OS or Mesos.
showing 71 - 80