Need advice about which tool to choose?Ask the StackShare community!
ArangoDB vs MarkLogic: What are the differences?
ArangoDB: A distributed open-source database with a flexible data model for documents, graphs, and key-values. A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions; MarkLogic: Schema-agnostic Enterprise NoSQL database technology, coupled w/ powerful search & flexible application services. MarkLogic is the only Enterprise NoSQL database, bringing all the features you need into one unified system: a document-centric, schema-agnostic, structure-aware, clustered, transactional, secure, database server with built-in search and a full suite of application services.
ArangoDB and MarkLogic can be primarily classified as "Databases" tools.
Some of the features offered by ArangoDB are:
- multi-model nosql db
- acid
- transactions
On the other hand, MarkLogic provides the following key features:
- Search and Query
- ACID Transactions
- High Availability and Disaster Recovery
"Grahps and documents in one DB" is the primary reason why developers consider ArangoDB over the competitors, whereas "RDF Triples" was stated as the key factor in picking MarkLogic.
ArangoDB is an open source tool with 8.22K GitHub stars and 576 GitHub forks. Here's a link to ArangoDB's open source repository on GitHub.
Hello All, I'm building an app that will enable users to create documents using ckeditor or TinyMCE editor. The data is then stored in a database and retrieved to display to the user, these docs can contain image data also. The number of pages generated for a single document can go up to 1000. Therefore by design, each page is stored in a separate JSON. I'm wondering which database is the right one to choose between ArangoDB and PostgreSQL. Your thoughts, advice please. Thanks, Kashyap
Which Graph DB features are you planning to use?
For a property and casualty insurance company, we currently use MarkLogic and Hadoop for our raw data lake. Trying to figure out how snowflake fits in the picture. Does anybody have some good suggestions/best practices for when to use and what data to store in Mark logic versus Snowflake versus a hadoop or all three of these platforms redundant with one another?
for property and casualty insurance company we current Use marklogic and Hadoop for our raw data lake. Trying to figure out how snowflake fits in the picture. Does anybody have some good suggestions/best practices for when to use and what data to store in Mark logic versus snowflake versus a hadoop or all three of these platforms redundant with one another?
As i see it, you can use Snowflake as your data warehouse and marklogic as a data lake. You can add all your raw data to ML and curate it to a company data model to then supply this to Snowflake. You could try to implement the dw functionality on marklogic but it will just cost you alot of time. If you are using Aws version of Snowflake you can use ML spark connector to access the data. As an extra you can use the ML also as an Operational report system if you join it with a Reporting tool lie PowerBi. With extra apis you can also provide data to other systems with ML as source.
Pros of ArangoDB
- Grahps and documents in one DB37
- Intuitive and rich query language26
- Good documentation25
- Open source25
- Joins for collections21
- Foxx is great platform15
- Great out of the box web interface with API playground14
- Good driver support6
- Low maintenance efforts6
- Clustering6
- Easy microservice creation with foxx5
- You can write true backendless apps4
- Managed solution available2
- Performance0
Pros of MarkLogic
- RDF Triples5
- JSON3
- Marklogic is absolutely stable and very fast3
- REST API3
- JavaScript3
- Enterprise3
- Semantics2
- Multi-model DB2
- Bitemporal1
- Tiered Storage1
Sign up to add or upvote prosMake informed product decisions
Cons of ArangoDB
- Web ui has still room for improvement3
- No support for blueprints standard, using custom AQL2
