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.
ArangoDB is flexible but still not so fast on complex tasks.
What do you like best about the product?
- Very flexible schema
- Support types of joining
- Integrated web UI is useful
- ArangoSearch View is easy to use and helpful in retrieving data from multiple collections, including exact and fuzzy searching
- Support types of joining
- Integrated web UI is useful
- ArangoSearch View is easy to use and helpful in retrieving data from multiple collections, including exact and fuzzy searching
What do you dislike about the product?
- Low performance on complex aggregations even when indexing is applied, especially on the big edge collections
- Documents do not describe how the index works clearly
- Graph traversal is not fast enough at times when filtering on edges. I needed to use 2 for loops (traverse 2 times) instead of multi-level traversing for better performance.
- Documents do not describe how the index works clearly
- Graph traversal is not fast enough at times when filtering on edges. I needed to use 2 for loops (traverse 2 times) instead of multi-level traversing for better performance.
What problems is the product solving and how is that benefiting you?
ArangoDB helped us to organize data pretty efficiently by providing multiple data models (especially the graph model) and an integrated search engine.
Cyber Threats data looks intuitive when being stored in ArangoDB
Cyber Threats data looks intuitive when being stored in ArangoDB
- Leave a Comment |
- Mark review as helpful
For DBAs it is easy to manage
What do you like best about the product?
From a DBA perspective, ArangoDB is easy to install, update and manage. We are using the ArangoDB enterprise edition on Linux RedHat. For install and update we are using the rpm pakages.
The user friendly Customer Support responds quickly and helpfully. Hot-Backups uses hardlinks and can be done very fast.
The user friendly Customer Support responds quickly and helpfully. Hot-Backups uses hardlinks and can be done very fast.
What do you dislike about the product?
There is no point-in-time backup/restore solution available.
What problems is the product solving and how is that benefiting you?
We were looking for a fast and lean NoSQL database.
There is nothing like it! Scalable Graphs, Documents & Open Source
What do you like best about the product?
I found ArangoDB as I was looking for a graph database that was ready for an enterprise content managment system that could act as a general purpose datastore, that didn't break the bank, and had good reliability. Also important was a managed hosting support for my enterprise client.
The alternatives neo4j quoted me a ridiculous ~$70k per year, with no garuntee that their software would work if they ever went out of buisness which seemed likely with that price point. Other graph solutions werent really scalable or didn't have as useful of a datamodel.
Three years after writing my application for arangodb I am extremely happy with this choice and continue to find new ways to organize information either in real-world messy graphs or in highly scalable key-value stores.
The nice for engineers about using arango is that since the project is open source you can create issues on their database repo and talk with real engineers about solutions, or feature requests to further refine the product rather than some know-nothing sales person.
The alternatives neo4j quoted me a ridiculous ~$70k per year, with no garuntee that their software would work if they ever went out of buisness which seemed likely with that price point. Other graph solutions werent really scalable or didn't have as useful of a datamodel.
Three years after writing my application for arangodb I am extremely happy with this choice and continue to find new ways to organize information either in real-world messy graphs or in highly scalable key-value stores.
The nice for engineers about using arango is that since the project is open source you can create issues on their database repo and talk with real engineers about solutions, or feature requests to further refine the product rather than some know-nothing sales person.
What do you dislike about the product?
- I have found one or two troublesome phenomenon with the interplay between supported APIs. For instance one api doesn't have the ability to delete edges / nodes in AQL as here: https://stackoverflow.com/questions/51650374/why-vertex-removing-request-doesnt-remove-linked-edge-with-aql-in-arangodb
- Not much python support. I am using `arangoorm` which is very nice but community supported. Please make this an official feature! I also would find more use with a python `foxx` like server but I understand if thats not reasonable.
- Not much python support. I am using `arangoorm` which is very nice but community supported. Please make this an official feature! I also would find more use with a python `foxx` like server but I understand if thats not reasonable.
What problems is the product solving and how is that benefiting you?
I needed a robust datamodel that avoided static schema problems with databases like postgres
Arangodb & DigSecurity
What do you like best about the product?
Ease of integration, platform operational management
What do you dislike about the product?
nothing specifc at the moment, the platform is working graet
What problems is the product solving and how is that benefiting you?
it provides the best graph database in the market, as of today
Great product
What do you like best about the product?
The option to manage graph and collections in the same DB
What do you dislike about the product?
Their UI is not stable.
They can improve the graph visibily. For example if I want to see the node data, I need to "Edit" the node instead of just hover it
They can improve the graph visibily. For example if I want to see the node data, I need to "Edit" the node instead of just hover it
What problems is the product solving and how is that benefiting you?
Managing graph and collection use cases in same DB
Surprisingly versatile
What do you like best about the product?
When comparing ArangoDB to other vendors in the space (including ones with large Market Caps) Arango comes out as a better product with better features. Some of the built in features of AQL make it a superior product with other players in the space.
What do you dislike about the product?
As a smaller player in the space, it is more difficult to convince upper management to go with Arango instead of other vendors (they perceive as being better than Arango) in the space.
What problems is the product solving and how is that benefiting you?
The graphing features in Arango make it the best choice for our product.
Best all purpose database so far
What do you like best about the product?
I like that it is very versatile with its multi model approach, you have the power of document store with graph search, whch essentially allows you to do whatever you do with both document stores and with SQL databases, plus much more thanks to the graph traversal. The AQL language is very intuitive and so quick to learn. Speed is great too. It is easy to use for prototyping and it porvides you with good devops tool for cluster installation on kubernetes.
What do you dislike about the product?
I think FOXX services are not the best approach for microservices, from a software architecture standpoint. Although documentation is generlaly good, I found that node.js documentation is a bit lacking behind
What problems is the product solving and how is that benefiting you?
We need to disssect complex documents, and find connectins between parts of documents, arangoDB allows me to do that plus whatever else a standard applictaion does, like CRUD operations, all in one database engine.
ArangoDB offers a powerful and user-friendly experience, supported by a evolving community.
What do you like best about the product?
What I appreciate most about ArangoDB is its versatility and performance as a graph database, making it an excellent fit for our product's needs. The managed hosting solution offered through ArangoGraph significantly simplifies operations, providing an easy-to-use and reliable service that ensures our applications run smoothly without extensive database management requirements. Additionally, the responsive and helpful customer support team enhances the overall experience, ensuring any issues or questions are promptly addressed.
What do you dislike about the product?
ArangoDB impresses with its robust performance and managed hosting convenience. However, navigating its advanced features could be smoother with more extensive documentation. While its community is smaller compared to some other databases, growing this supportive network could enrich user resources and collaboration opportunities, enhancing the overall ArangoDB experience.
What problems is the product solving and how is that benefiting you?
ArangoDB serves as the backbone of our packaging data management, enabling us to efficiently evaluate recyclability and Extended Producer Responsibility (EPR) fee costs of packaging in accordance with country-specific regulations. By leveraging ArangoDB's robust graph database capabilities, we can intricately map and analyze the complex relationships between various packaging materials, regulations, and fees. This not only streamlines our data processing but also enhances the accuracy and speed at which we can provide actionable insights to our clients.
ArangoDB for performant, streamlined data development beyond RDBMS or other NoSQL stores
What do you like best about the product?
ArangoDB offers a performant graph data model that offers some key benefits for almost any kind of data structure—not just graph theory applications. ArangoDB and its graph implementation allows you to think about entities semantically, and as standalone objects. Because edges in the graph are distinct from vertices, you can reason about data in isolation from how you or other teams want to create entity relationships.
IME this is a significantly streamlined approach to development, rather than complex ERD diagrams, foreign key constraints, foreign keys added to all tables, etc. that you'd normally use in an RDBMS/SQL setup. There is significant freedom in avoiding the RDBMS model and shoe-horning different data models beneath the same old SQL syntax.
ArangoDB also is trivial to start up via Docker, has a build-in UI that offers all of the fundamentals, and most of what you'd want outside of more hardcore analysis or data UIs. Implementing any size of cloud instance is trivial, and their datacenter locality is now quite good.
ArangoDB uses a performant K/V store based on RocksDB under the covers, including inverted index search out of the box, transactions, dynamic sharding. ArangoDB covers any database need I've had working with B2B/C SaaS products and services, all with a clean built-in interface and easier/possible to scale unlike many problematic document stores that are now rebranding as vector stores rather than (IMHO) getting their fundamentals fixed.
IME this is a significantly streamlined approach to development, rather than complex ERD diagrams, foreign key constraints, foreign keys added to all tables, etc. that you'd normally use in an RDBMS/SQL setup. There is significant freedom in avoiding the RDBMS model and shoe-horning different data models beneath the same old SQL syntax.
ArangoDB also is trivial to start up via Docker, has a build-in UI that offers all of the fundamentals, and most of what you'd want outside of more hardcore analysis or data UIs. Implementing any size of cloud instance is trivial, and their datacenter locality is now quite good.
ArangoDB uses a performant K/V store based on RocksDB under the covers, including inverted index search out of the box, transactions, dynamic sharding. ArangoDB covers any database need I've had working with B2B/C SaaS products and services, all with a clean built-in interface and easier/possible to scale unlike many problematic document stores that are now rebranding as vector stores rather than (IMHO) getting their fundamentals fixed.
What do you dislike about the product?
I really don't have dislikes, but there are a couple of things that they could add in the future to improve:
* When introduced in 2020ish, their cloud service (then called Oasis) had some issues with memory usage and silent lockups of Coordinators. That has since been resolved and they're adding more and more observability and resilience every year.
* They're working on a new replication system, which hopefully can be used as a powerful source for event streaming for auditing, ETL, or other purposes.
Other notes:
* I'm not convinced that ArangoDB should add vector store capability (I'd want a separate instance to separate the load profile anyway). It may help from a marketing perspective with the current state of the ebb and flow of AI buzz, but I'd rather it not come at the cost of existing core functionality.
* While the API offers K/V functionality, performing queries or graph traversals requires writing AQL queries. AQL is very powerful, but there's a learning curve, especially if you're used to SQL. As a SQList, you might at first think that "FOR vertex IN collection; FILTER vertex.valid == true;" is going to perform a table scan and filter, for example. But spending the time will reveal some very powerful functionality not possible with SQL.
* When introduced in 2020ish, their cloud service (then called Oasis) had some issues with memory usage and silent lockups of Coordinators. That has since been resolved and they're adding more and more observability and resilience every year.
* They're working on a new replication system, which hopefully can be used as a powerful source for event streaming for auditing, ETL, or other purposes.
Other notes:
* I'm not convinced that ArangoDB should add vector store capability (I'd want a separate instance to separate the load profile anyway). It may help from a marketing perspective with the current state of the ebb and flow of AI buzz, but I'd rather it not come at the cost of existing core functionality.
* While the API offers K/V functionality, performing queries or graph traversals requires writing AQL queries. AQL is very powerful, but there's a learning curve, especially if you're used to SQL. As a SQList, you might at first think that "FOR vertex IN collection; FILTER vertex.valid == true;" is going to perform a table scan and filter, for example. But spending the time will reveal some very powerful functionality not possible with SQL.
What problems is the product solving and how is that benefiting you?
ArangoDB provides a mechanism for modeling and querying data in a far more intuitive way than RDBMS or other graph/document stores. It streamlines discussions and maintenance of schema and requires less documentation and onboarding overhead.
Created by developers for developers
What do you like best about the product?
The whole team has said over and over how intuitive the Arango query language is. The threshold for learing it was extremely low and we even have frontend developers writing queries the few times they need something special, instead of coming to the backend developers asking for help to retrieve data from our SQL database.
The combination of a document and graph database suits us perfecetly, as our data has lots of connection to each other and in several levels and at the same time we need to be able to aggregate data over periods of time.
We are currently in the process of migrating all data from an SQL database to ArangoDB with the goal of completely getting rid of the SQL database and those cumbersome SQL queries.
Customer support has been quick to respond the few tickets we have had, even though the tickets have been marked with lowest priority by us when submitting the ticket.
The combination of a document and graph database suits us perfecetly, as our data has lots of connection to each other and in several levels and at the same time we need to be able to aggregate data over periods of time.
We are currently in the process of migrating all data from an SQL database to ArangoDB with the goal of completely getting rid of the SQL database and those cumbersome SQL queries.
Customer support has been quick to respond the few tickets we have had, even though the tickets have been marked with lowest priority by us when submitting the ticket.
What do you dislike about the product?
It was a bit of a learning curve on how data is sharded over the nodes in the cluster, which is essential to know in order to get good performance when executing queries.
While it's seldom you want to change name of a collection, that is however possible when working with a single standalone server, but it's not possible in a cluster setup.
It's not possible to set preferred service hours for maintenance (upgrades) for the clusters in their cloud service, so unless we're initiating upgrades manually they can start during our primetime.
While it's seldom you want to change name of a collection, that is however possible when working with a single standalone server, but it's not possible in a cluster setup.
It's not possible to set preferred service hours for maintenance (upgrades) for the clusters in their cloud service, so unless we're initiating upgrades manually they can start during our primetime.
What problems is the product solving and how is that benefiting you?
As our data is very connected to each other, and in many levels, the graph part helps us to quickly traverse and retrieve data. The query language is very powerful and intuitive and performance (at least for our needs) is on par with SQL databases, so we are migrating all data to Arango, as well as all our queries for aggregating data with the goal to completely replace SQL with ArangoDB.
showing 1 - 10