Google Cloud Datastore is a NoSQL "schemaless" database as a service, supporting diverse data types. The database is managed; Google manages sharding and replication and prices according to storage and activity.
N/A
Progress MarkLogic
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
Google Cloud Datastore
Progress 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
Google Cloud Datastore
Progress MarkLogic
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Google Cloud Datastore
Progress MarkLogic
Considered Both Products
Google Cloud Datastore
Verified User
Anonymous
Chose Google Cloud Datastore
As stated before, we eventually chose Google Cloud Datastore because we were already leveraging other Google Cloud services like VMs, Cloud Runs, logging etc. MySQL and MongoDB were possible alternatives, but we preferred to lock in to the Google ecosystem.
We selected Google Cloud Datastore as one of our candidates for our NoSQL data is because it is provided by Google Cloud, which fits our needs. Most of our infrastructure is on Google Cloud, so when we think about the NoSQL database, the first thing we thought about is Google …
If deploying an application in Google Cloud Platform, using Google Cloud Datastore is a no brainer because of the simplicity of setup. Other options would require more setup and configuration, and do not come with the same level of guaranteed uptime as Google Cloud Datastore. …
In comparison to both Mongo and HBase, MarkLogic wins in terms of integration to other systems, while loosing in terms of pricing. In terms of documentation all will be in same range putting MarkLogic a bit forward.
MarkLogic is good at what it does: storing and searching XML with a REST interface. The amount of support out there for the other NoSQL products is what gives them the best advantage. Many plugins exist for those, none exist for MarkLogic. Even the proprietary ones like …
There's no other single product that directly compares to all the features that are packed into MarkLogic. Generally speaking, you're looking at a combination of many products to build a stack that competes feature-for-feature. Even if you're leveraging only a limited set of …
I have used most of the common RDBMS databases (SQL Server, Oracle, MySQL, etc.). MarkLogic is more dependable, faster, and flexible. I would not willingly go back to RDBMS. As far as open source competition to MarkLogic such as MongoDB, I haven't used it myself so I don't have …
Senior Director, IT Architecture and Publishing Solutions
Chose Progress MarkLogic
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 …
If you want a serverless NoSQL database, no matter it is for personal use, or for company use, Google Cloud Datastore should be on top of your list, especially if you are using Google Cloud as your primary cloud platform. It integrates with all services in the Google Cloud platform.
In an area where it will be built once and maintained, it shines. If you aim to use CI, temporary environments, or anything else, it is not very effective. Licensing is almost impossible on boxes that are to be created on the fly.
Indexing is a major strength of MarkLogic. The out-of-the-box configuration is set up to handle a combination of text and fielded data. The indexing is also highly configurable. Those configuration options are at the heart of a lot of our high-volume, high-performance applications.
The industrial strength transactions and security are also a strength, particularly when we are dealing with user-created intellectual property.
The engineering support is a strength. They are big enough to have a really strong support and engineering staff, but small enough so that a medium-sized customer has access to it. They are very responsive to questions and problem reports.
The ability to move easily among XML and JSON is a strength.
How to do complete data profiling on documents loaded in Marklogic database?
Customers need a tools which can be customized to suit their data profiling needs but currently the tools which MarkLogic provides fall short on this requirement.
Unit testing framework which is using only XQuery as the language is lacking some features.
For the amount of use we're getting from Google Cloud Datastore, switching to any other platform would have more cost with little gain. Not having to manage and maintain Google Cloud Datastore for over 4 years has allowed our teams to work on other things. The price is so low that almost any other option for our needs would be far more expensive in time and money.
Our firm has consultants for a number of technologies/disciplines. While I am capable and experienced in other areas, my preference is always to work on engagements with MarkLogic. As an architect and developer, I get far more flexibility and performance from one product instead of cobbling together a stack of several products to provide a capability that MarkLogic has rolled into one great product.
The simple implementation, together with the Google Cloud dashboard that allows data inspection, editing and querying, makes Google Cloud Datastore a comprehensive choice when it comes to NoSQL databases.
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.
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.
As stated before, we eventually chose Google Cloud Datastore because we were already leveraging other Google Cloud services like VMs, Cloud Runs, logging etc. MySQL and MongoDB were possible alternatives, but we preferred to lock in to the Google ecosystem.
In comparison to both Mongo and HBase, MarkLogic wins in terms of integration to other systems, while loosing in terms of pricing. In terms of documentation all will be in same range putting MarkLogic a bit forward.
It took longer than expected to develop our application and get the level of consistent performance necessary. As a result, profit was flat for a couple of years but the benefits are really starting to kick in.