ArangoGraph (Managed Service)
ArangoDBReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
108 reviews
from
External reviews are not included in the AWS star rating for the product.
A great graph database
What do you like best about the product?
I tried different graph databases and ArangoDB provides an interesting interface with a good speed. It was lacking of a Ruby driver, but thanks of their amazing documentation it was really easy to create a basic one.
What do you dislike about the product?
The creation of a cluster with ArangoDB without using Mesos or DC/OS didn't seem of easy implementation.
What problems is the product solving and how is that benefiting you?
ArangoDB provides a good speed and an interesting way to manage the database with the power of graph theory. To make connection by a schema provides an easy solution to a hard storage problem as the connection between the objects.
Recommendations to others considering the product:
I like the graph quality of ArangoDB and I enjoy to create the Ruby gem ArangoRB by using their HTTP API. AQL is a powerful language, easy to learn and with good examples. ArangoDB is a poweful tool that have the potentiality to continue to grow.
OpenSource Graph Database for the Masses
What do you like best about the product?
ArangoDB is a very transparent and open-source friendly application with tons of great features and a friendly community.
What do you dislike about the product?
Though the community is friendly and the documentation that exists is good, both are severely lacking. Focus on availability of advanced documentation (specifically around AQL) and community involvement would drastically improve the use-case of beginners and advanced developers using AraingoDB.
What problems is the product solving and how is that benefiting you?
We are using ArangoDB for our entire back-end database at https://www.zooxoos.com/
Using Scarango (https://github.com/outr/scarango) driver we've been able to retain great type-safety without sacrificing the flexibility offered in a document database.
Using Scarango (https://github.com/outr/scarango) driver we've been able to retain great type-safety without sacrificing the flexibility offered in a document database.
Recommendations to others considering the product:
It may take a little more effort to get going with ArangoDB in the short-run and grasp the benefits of a graph database, but it's definitely worth the time.
Fast and very flexible multi-model database
What do you like best about the product?
Ability to combine graph model and document store gives us the flexibility we need to run our core processes and improve it very efficiently
What do you dislike about the product?
Foxx application are very useful but the lack of integration with external applications (like an Event Queue System) leads us to separate a single core model application into 2 or 3 applications
What problems is the product solving and how is that benefiting you?
eLamp provides a way for companies to build a very flexible skill mapping of the company. HR managers create and maintain Skill mapping, include their KPI on each skill, in a way that project managers and collaborators can use it to build the perfect team for a project or find an expert.
We had to have a very flexible and fast data model with realtime analysis so Graph Data Model was our requirement.
We had to have a very flexible and fast data model with realtime analysis so Graph Data Model was our requirement.
The best approach available for a Multimodel DB!
What do you like best about the product?
As the creator of nosql-database.org, I tested about 80 NoSQL Databases. ArangoDB is by far the best DB for the multimodel world. Awesome graph features, scalable, and ready for the microservice world. Top recommendation!
What do you dislike about the product?
As ArangoDB has nearly all features available I do have no dislike but simply some missing features: a book (although the doc is great), native C, C++ (fast) code integration and native bitemporal features.
What problems is the product solving and how is that benefiting you?
We do have datasets which are K/V, and JSON. Then we need to dig out graph connections, integrate them and query them. Perfect for ArangoDB, as you only need to admin one DB!
Recommendations to others considering the product:
Use the Docker image and you can test in seconds!!
A fast, flexible, multi-mode database
What do you like best about the product?
Having the option for combined graph and document store was just what we needed. We were replacing a Mysql implementation of our product. Replacing the iterative collection of data with a graph traversal improved performance 1000x. The document store added considerable flexibility for our customers. Foxx added an additional performance boost.
What do you dislike about the product?
Debugging a Foxx application is painful. There are no debuggers so you start relying on console output. Foxx also doesn't have a way to bind native code or to launch external programs like node.js. This means that we couldn't implement the full business logic in Foxx.
What problems is the product solving and how is that benefiting you?
We have a product that we've been marketing for ~15 years. Because of the fixed schema it was difficult to implement new features in a backwards compatible fashion. With the flexibility of ArangoDB, we were not only able to dramatically improve performance, but we were no longer constrained to a fixed schema. This helps future-proof the product. It also allows us to have a well-defined API for customers.
Recommendations to others considering the product:
If you have an application that can benefit from a graph database I highly recommend it. If you need a combined graph/document store then you must take a look at this. I would recomment that you take the time to learn AQL when evaluating it. Once you get comfortable with it, you'll see how powerful it is.
Easy to learn and use, light on system, helpful people
What do you like best about the product?
These guys really do add nice things here that you didn't know you needed. They make good choices. They don't try to do everything. (although multi-model gives you a lot along with FOXX) A very friendly license.
What do you dislike about the product?
Mostly I wish there were more language bindings and traction in the community. More and bigger examples and some books would make me happy.
What problems is the product solving and how is that benefiting you?
I am using this to manage data in QA Automation workflows. It is so capable and flexible and easy to bring up and start using. This has allowed me to store data outside our Jenkins CI and outside of our Git repository for both temporary and long term use. The flexible structure is of course super in letting me adjust things quickly to what I need to keep my QA Automations working.
Recommendations to others considering the product:
When you want a friendly license, built in admin & access controls, performance (not built on Java) and well thought out features that work. Look to ArangoDB. This will get you up and running fast, and it will leave you with lots of options to keep working. This is not a one-trick-pony, but a very very capable tool. Just working with it as a JSON document database and using one of the several excellent Python language bindings, then figuring out queries as I go, it is just great to work with. AQL makes more sense when you realize it's all about the JSON and it works out really well with Python (and of course very natively in JavaScript apps). If you are doing work in JavaScript, this is a fabulous tool to turn to. I am really looking forward to the benefits this will bring long term. I am curious how well I can get things integrated to other tools like Elastic Search.
There are so many friendly tools built in. They are very discoverable and continue to be useful even after you have learned a lot.
There are so many friendly tools built in. They are very discoverable and continue to be useful even after you have learned a lot.
Powerful, fast, and keeps getting better
What do you like best about the product?
For starters, you can be up and running in minutes. While there are many advanced configuration options, getting a basic installation at a usable level it trivial. Being able to move back and forth between document and graph databases is a huge plus. It is VERY fast and the AQL language is incredibly powerful.
What do you dislike about the product?
There are places where the documentation is somewhat lacking. It is improving to be sure, but there is still opportunity for improvement.
What problems is the product solving and how is that benefiting you?
As the back-end for a cryptographic key and certificate management system, it is management of incredibly complex and multi-faceted data--and mapping relationships within that data--a quantifiable, repeatable task. AQL queries alone have saved countless hours of effort.
Recommendations to others considering the product:
Take the time to read *all* of the documentation as well as the community driven Cookbook.
The best multi-model database
What do you like best about the product?
Multi -model concept is a nice-to-have feature for a database.
Storing documents and graphs allows users to have a single place where to store theirs data and query them in multiple ways.
ArangoDB provides a query language (AQL) similar to SQL for querying the data.
ArangoDB provides also a microservices framework named Foxx : you can add some business logic that is executed in the database (performance benefits).
Storing documents and graphs allows users to have a single place where to store theirs data and query them in multiple ways.
ArangoDB provides a query language (AQL) similar to SQL for querying the data.
ArangoDB provides also a microservices framework named Foxx : you can add some business logic that is executed in the database (performance benefits).
What do you dislike about the product?
A specific AQL shell is missing (you have to embed your queries in Javascript).
What problems is the product solving and how is that benefiting you?
The main problem was how to store complex data with an evolutive (moving frequently) schema.
ArangoDB provides a simple way to store theses kind of documents in a simple way.
ArangoDB provides a simple way to store theses kind of documents in a simple way.
showing 101 - 108