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.
A very powerful database to build scalable apps
What do you like best about the product?
Foxx
With Foxx you can create Restful API directly in the heart of the database. You save HTTP requests and it's very fast. You API will scale with your cluster.
You can even run scripts in background using queues (for email sending by example)
Graph
You can create graph and use them very easily.
AQL
The AQL language is very easy to understand. The learning curve is short.
JOINS
In one request you can get the data you want.
With Foxx you can create Restful API directly in the heart of the database. You save HTTP requests and it's very fast. You API will scale with your cluster.
You can even run scripts in background using queues (for email sending by example)
Graph
You can create graph and use them very easily.
AQL
The AQL language is very easy to understand. The learning curve is short.
JOINS
In one request you can get the data you want.
What do you dislike about the product?
Nothing for now. I can do anything I want with this database.
I didn't test yet the rocksdb storage ... So I can't tell about performances using it.
I didn't test yet the rocksdb storage ... So I can't tell about performances using it.
What problems is the product solving and how is that benefiting you?
I can create app faster, I even wrote a tool to simplify my life : https://foxx-framework.com
I now use full JS stack from frontend (vueJS, riotJS) to backend (Foxx)
The graph feature saved me some intensive CPU for manipulating trees.
It's very easy to start a new project using this database.
I now use full JS stack from frontend (vueJS, riotJS) to backend (Foxx)
The graph feature saved me some intensive CPU for manipulating trees.
It's very easy to start a new project using this database.
Recommendations to others considering the product:
It worth to play with it ... Once get confortable with Foxx, AQL 1 Graph you won't go back
Exceeded Expectations
What do you like best about the product?
The query language, AQL, of course! I often found myself doing things in AQL that I would have before used a programming language.
What do you dislike about the product?
Because it is young, there is less community support and fewer third-party packages available.
What problems is the product solving and how is that benefiting you?
About the Project:
Meta-Research Engine is a software system with the purpose of facilitating the mass encoding of scientific research studies. Define a research project, upload a set of papers under the domain of interest, and invite encoders to collaborate in extracting their information. At the end of a project, you are left with a reliable data set encompassing the contents of many research papers.
Meta-Research Engine is a software system with the purpose of facilitating the mass encoding of scientific research studies. Define a research project, upload a set of papers under the domain of interest, and invite encoders to collaborate in extracting their information. At the end of a project, you are left with a reliable data set encompassing the contents of many research papers.
An excellent, complete and reliable database for easy learning and use
What do you like best about the product?
Very flexible that does not force the user to focus only on a single data model.
key/values, documents or graphs in the same database and possibility of using everything simultaneously!
It is very noticeable that its creators have a deep knowledge of different types of databases.
It is very easy to understand the concepts of this database. The query language is very powerful and easy to understand. Extensive documentation that helps you practice and use ArangoDB in the coming hours!
Our projects (accouting, web applications, budgets) are very complex and we need a multi-model approach. In other databases we do not have this opportunity.
This database has a good technical support. ArangoDB regularly organizes webinars and training. The product is well maintained and the company is able to create several upgrades (version) in one year!
ArangoDB is fully ready for the production environment.
It is very nice that the company gives you all the time you need to test this database.
We have never felt pressured by the evaluation period that in the case of ArangoDB is unlimited.
key/values, documents or graphs in the same database and possibility of using everything simultaneously!
It is very noticeable that its creators have a deep knowledge of different types of databases.
It is very easy to understand the concepts of this database. The query language is very powerful and easy to understand. Extensive documentation that helps you practice and use ArangoDB in the coming hours!
Our projects (accouting, web applications, budgets) are very complex and we need a multi-model approach. In other databases we do not have this opportunity.
This database has a good technical support. ArangoDB regularly organizes webinars and training. The product is well maintained and the company is able to create several upgrades (version) in one year!
ArangoDB is fully ready for the production environment.
It is very nice that the company gives you all the time you need to test this database.
We have never felt pressured by the evaluation period that in the case of ArangoDB is unlimited.
What do you dislike about the product?
I have nothing to dislike!
At this time, this database covers all our production project needs.
Honestly and responsibly I would say that this database deserves one of the best positions in the market.
At this time, this database covers all our production project needs.
Honestly and responsibly I would say that this database deserves one of the best positions in the market.
What problems is the product solving and how is that benefiting you?
Without any doubt, performance. The best NoSQL databases fail to make the joins that ArangoDB does.
In the world of databases is obvious and correct a multimodel approach.
In the world of databases is obvious and correct a multimodel approach.
Recommendations to others considering the product:
If you are interested in NoSQL database but you have the "SQL mind", this is your big chance! ArangoDB will not fail!
Best database solution nowadays!
What do you like best about the product?
FLEXIBLE
Combination of document-, key-value- and graph database, truly genius!
FAST
With Foxx Services, I can make complex queries directly on the database, no bottle-neck like conventional backend and database communication.
BEAUTIFUL
I never saw a beautifully and also function Admin Interface for ANY database I used before.
Combination of document-, key-value- and graph database, truly genius!
FAST
With Foxx Services, I can make complex queries directly on the database, no bottle-neck like conventional backend and database communication.
BEAUTIFUL
I never saw a beautifully and also function Admin Interface for ANY database I used before.
What do you dislike about the product?
No FeathersJS Integration yet :(
Only found adapters for Waterline and LoopbackJS
Only found adapters for Waterline and LoopbackJS
What problems is the product solving and how is that benefiting you?
We built a multilevel marketing system, for this solution we needed graphs.
Right now we are developing a food guide app which uses a lot of food and food data. For better data usage we want to use semantic linking.
Right now we are developing a food guide app which uses a lot of food and food data. For better data usage we want to use semantic linking.
Recommendations to others considering the product:
Use it :)
Hidden champion
What do you like best about the product?
The overall stability, extensive choice of API's and the performance.
What do you dislike about the product?
Some very interesting features are now "Enterprise only" - but hey, somebody has to earn some money!
What problems is the product solving and how is that benefiting you?
Having a multi-model database solved a lot of system architecture problems for us.
ArangoDB is my database for everything
What do you like best about the product?
AQL! Literally the easiest and easiest to understand query language I've used as of yet.
What do you dislike about the product?
Nothing yet. ArangoDB seems to keep saying yes to everything I want to do.
What problems is the product solving and how is that benefiting you?
The primary product I use ArangoDB for (vlllage.com) was suffering from sluggishness due to unoptimized querying on Google's App Engine, it was getting to the point where a single page load could take up to 30 seconds and I had to do something about it, so I looked around and decided to try ArangoDB. Could not be happier! Page loads are insanely snappy, and the setup was actually quite easy.
They also have a very nice admin interface. The primary query of the app (geo-locate + join relations + filter + sort by distance) needs zero workarounds. I now use ArangoDB for all new projects going forward.
They also have a very nice admin interface. The primary query of the app (geo-locate + join relations + filter + sort by distance) needs zero workarounds. I now use ArangoDB for all new projects going forward.
Recommendations to others considering the product:
Go for it, you won't go back.
With great flexibility, comes great power
What do you like best about the product?
Super efficient Multi-Model engine. Having a schemaless db is definitely a positive in this day and age of MVP, but one that can efficiently perform all aspects of common development and business logic woes, is a rare find. I've had my faith in ArangoDb for over 3 years now, after being burnt by several Db's, MongoDB included. Not until recently have I really started to aggressively use it, and I am so excited to know that it's passing all my requirements I feel I can deliver a product that will scale and enable me to compete with some of the biggest names out there at a fraction of the time and cost!
What do you dislike about the product?
Too much freedom! When confronted with a multi-model approach, it's easy to separate your data across the models as one would think appropriate. However, it's often the case that the data is actually used differently based on the different circumstances, something that I learnt rather than got guided on. I do feel you are left to swim on your own in this sea of possibility. And it has taken me 10's of hours to understand it. Whilst the Arango team are there on Slack, I feel there should be more 'instructors' who can advise on how to use the technology best to the problems a new user may face rather than focus on the technical questions / issues. I had nearly lost faith and settled on what I considered a poor performing query but, through persisting for hours, I go the result I wanted...but those 10hrs+ could have been saved perhaps if an Arango team member just gave .a little guidance to how best their tool would perform in the area I was researching...
What problems is the product solving and how is that benefiting you?
Rapid development == schemaless. Social network == graph, Advanced Filters == embedded properties. Whilst several databases out there all deal with these individual components, finding one that conglomerates them all effectively means ubiquity. Writing a social platform the basics of the MVP require you can focus development on the problem at hand, not ensuring systems are all talking.
ArangoDB has allowed not only to keep my workspace simple but it's Foxx service allows for quick API generation (has it's own swagger interface to quickly test your endpoints). I am now able to focus on the business features, and minimise cross-language issues as it's uses Javscript for it's data projection
ArangoDB has allowed not only to keep my workspace simple but it's Foxx service allows for quick API generation (has it's own swagger interface to quickly test your endpoints). I am now able to focus on the business features, and minimise cross-language issues as it's uses Javscript for it's data projection
Recommendations to others considering the product:
Persevere! It takes time to realise that you have complete flexibility over your data model. Don't constrain yourself to one model. A recent task, showed that whilst I had a graph model for one aspect, also applying a document model to the problem, I reduced search time from ~2seconds to ~1ms due to effective use of being able to use indexes on embedded document arrays! The data was effectively duplicated as edges as well as being with the document, but it was about 20bytes per document totalling 230kb.
The edge connections are still important for traversal, data mining purposes. So...approach the problem multi-model fold, and you'll really make the most of ArangoDB as it's intended.
The edge connections are still important for traversal, data mining purposes. So...approach the problem multi-model fold, and you'll really make the most of ArangoDB as it's intended.
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.
showing 101 - 110