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.
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 :)
- Leave a Comment |
- Mark review as helpful
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.
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.
showing 81 - 90