TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache Geode

    Score7 out of 10
    N/AApache Geode is a distributed in-memory database designed to support low latency, high concurrency solutions, available free and open source since 2002. With it, users can build high-speed, data-intensive applications that elastically meet performance requirements. Apache Geode blends techniques for data replication, partitioning and distributed processing.N/A

    Progress MarkLogic

    Score9 out of 10
    N/AMarkLogic 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 GeodeProgress MarkLogic
    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
    Apache GeodeProgress MarkLogic
    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
    Features
    Apache GeodeProgress MarkLogic
    NoSQL Databases
    Comparison of NoSQL Databases features of Apache Geode and Progress MarkLogic
    Feature
    Apache Geode
    8.7
    1 Ratings
    2% above category average
    Progress MarkLogic
    7.9
    2 Ratings
    8% below category average
    Performance9.01 Ratings8.52 Ratings
    Availability10.01 Ratings8.02 Ratings
    Concurrency10.01 Ratings7.52 Ratings
    Scalability8.01 Ratings8.52 Ratings
    Data model flexibility7.01 Ratings7.02 Ratings
    Deployment model flexibility8.01 Ratings6.52 Ratings
    Security00 Ratings9.02 Ratings
    Best Alternatives
    Apache GeodeProgress MarkLogic
    Small Businesses
    IBM Cloudant
    Score7.4 out of 10
    IBM Cloudant
    Score7.4 out of 10
    Medium-sized Companies
    IBM Cloudant
    Score7.4 out of 10
    IBM Cloudant
    Score7.4 out of 10
    Enterprises
    IBM Cloudant
    Score7.4 out of 10
    IBM Cloudant
    Score7.4 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Apache GeodeProgress MarkLogic
    Likelihood to Recommend
    7.0
    (1 ratings)
    9.0
    (7 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    7.0
    (7 ratings)
    Usability
    8.0
    (1 ratings)
    9.0
    (1 ratings)
    Support Rating
    1.0
    (1 ratings)
    9.0
    (1 ratings)
    User Testimonials
    Apache GeodeProgress MarkLogic
    Likelihood to Recommend
    Apache
    The biggest advantage of using Apache Geode is DB like consistency. So for applications whose data needs to be in-memory, accessible at low latencies and most importantly writes have to be consistent, should use Apache Geode. For our application quite some amount of data is static which we store in MySQL as it can be easily manipulated. But since this data is large R/w from DB becomes expensive. So we started using Redis. Redis does a brilliant job, but with complex data structures and no query like capability, we have to manage it via code. We are experimenting with Apache Geode and it looks promising as now we can query on complex data-structures and get the required data quickly and also updates consistent.
    Incentivized
    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.
    Incentivized
    Read full review
    Pros
    Apache
    • Super Fast data pull/push
    • Provided ACID transactions, so it works like a SQL Database
    • Provides replication & partitioning, so our data is never lost and extraction is super fast. NoSql like properties
    Incentivized
    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.
    Incentivized
    Read full review
    Cons
    Apache
    • Needs more supporting languages. Out of box Python, Nodejs adapters would be wonderful
    • Currently it supports just KV Store. But if we could cache documents or timeseries data would be great
    • Needs more community support, documentation.
    Incentivized
    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.
    Incentivized
    Read full review
    Likelihood to Renew
    Apache
    No answers on this topic
    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.
    Incentivized
    Read full review
    Usability
    Apache
    Still Experimenting. Initial results are good. we need to figure out if we can completely replace Redis. Cost wise if it makes sense to keep both or replacement is feasible.
    Incentivized
    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.
    Incentivized
    Read full review
    Support Rating
    Apache
    Never contacted support
    Incentivized
    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.
    Incentivized
    Read full review
    Alternatives Considered
    Apache
    Still Experimenting. But looks promising as it has query capabilities over complex data structures
    Incentivized
    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.
    Incentivized
    Read full review
    Return on Investment
    Apache
    • Still experimenting so difficult to quote
    • For a small size project/teams might be an overkill as it still has certain learning curve
    • For Medium to large projects with complex Data Structures that need to be queried with a fast o/p it definitely works
    Incentivized
    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.
    Incentivized
    Read full review
    ScreenShots