Apache Cassandra vs. MarkLogic Server

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Cassandra
Score 7.7 out of 10
N/A
Cassandra is a no-SQL database from Apache.N/A
MarkLogic Server
Score 9.0 out of 10
N/A
MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. The vendor states it is the most secure multi-model database, and it’s deployable in any environment. They state it is an ideal database to power a data hub.
$0.01
per MCU/per hour + 0.10 per GB/per month
Pricing
Apache CassandraMarkLogic Server
Editions & Modules
No answers on this topic
Low Priority Fixed
$0.01
per MCU/per hour + 0.10 per GB/per month
Standard Reserved
$0.07
per MCU/per hour + 0.10 per GB/per month
Standard On-Demand
$0.13
per MCU/per hour + 0.10 per GB/per month
Offerings
Pricing Offerings
CassandraMarkLogic Server
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache CassandraMarkLogic Server
Top Pros
Top Cons
Features
Apache CassandraMarkLogic Server
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache Cassandra
8.0
5 Ratings
9% below category average
MarkLogic Server
7.9
2 Ratings
11% below category average
Performance8.55 Ratings8.52 Ratings
Availability8.85 Ratings8.02 Ratings
Concurrency7.65 Ratings7.52 Ratings
Security8.05 Ratings9.02 Ratings
Scalability9.55 Ratings8.52 Ratings
Data model flexibility6.75 Ratings7.02 Ratings
Deployment model flexibility7.05 Ratings6.52 Ratings
Best Alternatives
Apache CassandraMarkLogic Server
Small Businesses
IBM Cloudant
IBM Cloudant
Score 8.2 out of 10
IBM Cloudant
IBM Cloudant
Score 8.2 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 8.2 out of 10
IBM Cloudant
IBM Cloudant
Score 8.2 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 8.2 out of 10
IBM Cloudant
IBM Cloudant
Score 8.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache CassandraMarkLogic Server
Likelihood to Recommend
6.0
(16 ratings)
9.0
(7 ratings)
Likelihood to Renew
8.6
(16 ratings)
7.0
(7 ratings)
Usability
7.0
(1 ratings)
9.0
(1 ratings)
Support Rating
7.0
(1 ratings)
9.0
(1 ratings)
Implementation Rating
7.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apache CassandraMarkLogic Server
Likelihood to Recommend
Apache
Apache Cassandra is a NoSQL database and well suited where you need highly available, linearly scalable, tunable consistency and high performance across varying workloads. It has worked well for our use cases, and I shared my experiences to use it effectively at the last Cassandra summit! http://bit.ly/1Ok56TK It is a NoSQL database, finally you can tune it to be strongly consistent and successfully use it as such. However those are not usual patterns, as you negotiate on latency. It works well if you require that. If your use case needs strongly consistent environments with semantics of a relational database or if the use case needs a data warehouse, or if you need NoSQL with ACID transactions, Apache Cassandra may not be the optimum choice.
Read full review
Progress Software
If you are storing META data then MarkLogic is super useful as it retrieves everything so fast, while storing the whole data shows performance issues some times. If you have legacy systems then migrating from it would really require sweat and blood, on the other hand if you are in systems like Node.js you can simply integrate two systems easily. If you don't know how in the end your your data schema will look like then it's better to make a prototype using MarkLogic.
Read full review
Pros
Apache
  • Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
  • Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
  • Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
  • Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.
Read full review
Progress Software
  • Search was really advanced. Hard to set up and had limitations about semantical meanings between xml nodes, but provided very good search abilities.
  • The organization of documents across collections and metadata was particularly useful.
  • The REST abilities were very advanced and worked with XQuery well.
Read full review
Cons
Apache
  • Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
  • Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
  • There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.
Read full review
Progress Software
  • MarkLogic still has a long way to go in fostering the developer community. Many developers are gravitating to the simple integrations and do not delve into the deeper capabilities. They have made tremendous strides in recent months and I am sure this will improve over time.
  • Many of the best features are left on the floor by enterprises who end up implementing MarkLogic as a data store. MarkLogic needs to help customers find ways to better leverage their investment and be more creative in how they use the product.
  • Licensing costs become a major hurdle for adoption. The pricing model has improved for basic implementations, but the costs seem very prohibitive for some verticals and for some of the most advanced features.
Read full review
Likelihood to Renew
Apache
I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.
Read full review
Progress Software
MarkLogic is expensive but solid. While we use open source for almost everything else, the backend database is too critically important. At this point, re-tooling for a different back end would take too much time to be a viable option.
Read full review
Usability
Apache
It’s great tool but it can be complicated when it comes administration and maintenance.
Read full review
Progress Software
Very little about it can be done better or with greater ease. Even things that seem difficult aren't really that bad. There's multiple ways to accomplish any admin task. MarkLogic requires a fraction of administrative effort that you see with enterprise RDBMS like Oracle. MarkLogic is continually improving the tools to simplify cluster configuration and maintenance.
Read full review
Support Rating
Apache
Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.
Read full review
Progress Software
There's always room for improvement. Some problems get solved faster than others, of course. MarkLogic's direct support is very responsive and professional. If they can't help immediately, they always have good feedback and are eager to receive information and details to work to replicate the problem. They are quick to escalate major support issues and production show-stopping problems. In addition to MarkLogic's direct support, there are several employees who are very active among the community and many questions and common issues get quick attention from helpful responses to email and StackOverflow questions.
Read full review
Alternatives Considered
Apache
We evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for web and mobile applications due to its performance concern. Cassandra, by contrast, offers the availability and performance necessary for developing highly available applications. Furthermore, the Hadoop technology stack is typically deployed in a single location, while in the big international enterprise context, we demand the feasibility for deployment across countries and continents, hence finally we are favor of Cassandra
Read full review
Progress Software
We had Fast in place when Microsoft had bought it up and was going to change / deprecate it. One of the biggest advantages of MarkLogic for search actually had to do with the rest of the content pipeline - it allowed us to have it all in one technology. On the NoSQL side, we looked at MongoDB a couple years back. At that time, MarkLogic came in stronger on indexing, transaction reliability, and DR options. For us, that was worth using a commercial product.
Read full review
Return on Investment
Apache
  • I have no experience with this but from the blogs and news what I believe is that in businesses where there is high demand for scalability, Cassandra is a good choice to go for.
  • Since it works on CQL, it is quite familiar with SQL in understanding therefore it does not prevent a new employee to start in learning and having the Cassandra experience at an industrial level.
Read full review
Progress Software
  • MarkLogic reduced the amount of time that the DevOps team needed to dedicate to database updates, as the engineering team was mostly able to easily design and maintain database upgrades without requiring specialists such as database architects on the DevOps side. This capability flowed from the product's speed and the versatility of its XQuery language and libraries.
  • MarkLogic required significant education and buy-in time for the engineering team.
Read full review
ScreenShots