We are using the solution for source data to put into a database to ingest all the data. We are using it to convert everything into a standard format. We use it to run over the content to ensure everything is running properly. It's great for ingesting data and standardizing everything.
Software Engineer at Thomson Reuters International Pvt. Ltd.
Good ROI, great for standardizing data, and reliable
Pros and Cons
- "The rules can show us if there are missing items, like titles, and we can add them in to ensure everything is filled and makes sense and there are no missing details."
- "The spreadsheet capabilities could be improved."
What is our primary use case?
How has it helped my organization?
At the code level, using the solution on elements or functions makes it easier to insert or manage data. There are lots of elements or functions that we can use to create and standardize data. It helps us to find specific data easily. It helps to have the raw data and files standardized.
Currently, we are working on medical policies, and we have to follow instructions for specific functions, and this makes it easier to ensure everything aligns.
What is most valuable?
We're dealing with multiple types of data, and this solution helps to standardize it. Once items are in a standard format, we can validate them.
If there are errors or a title is missing, we can still find a way to check the information and make the necessary changes.
If there are a lot of items missing, we can make out own rules. We can, for example, ensure that if a title is missing, we can put information in there manually if it is missing from the source material. The rules can show us if there are missing items, like titles, and we can add them in to ensure everything is filled and makes sense and there are no missing details.
Over the last years, we've been working on the data side, and have found things are going better and faster. We like that we can use NoSQL with it.
It is scalable.
The solution is stable.
Techncial support is fine.
What needs improvement?
The spreadsheet capabilities could be improved. We need to convert spreadsheets into an open XML format. We have to do a few levels of conversions before we convert the data into the information we require. It would be ideal if the process could be a bit more streamlined to simplify the process.
When we convert to XML, there's a lot of unnecessary data, and we have to manually clean up everything before we can really dig in.
The solution is expensive.
Buyer's Guide
MarkLogic
March 2026
Learn what your peers think about MarkLogic. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
884,976 professionals have used our research since 2012.
For how long have I used the solution?
We've been using the solution for one year.
What do I think about the stability of the solution?
It is stable and reliable. That said, it can take some time to load the product.
What do I think about the scalability of the solution?
The solution is scalable. Users can expand the product. However, it depends on the server design.
How are customer service and support?
The solution's technical support is fine. We've reached out to them in the past.
How was the initial setup?
The initial setup is pretty straightforward. It's easy.
What was our ROI?
We've witnessed a pretty good ROI. The investment has been worth it for us.
What's my experience with pricing, setup cost, and licensing?
It's a costly product. However, their reputation justifies the cost. It's a trusted product.
What other advice do I have?
I'm an end-user.
Many high-level companies are using the solution. It's a trusted product. The product offers very good technology, and the features have been quite useful.
I'd rate the solution nine out of ten. I'm quite happy with its capabilities. It's very innovative.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Consistent monitoring has ensured long-running batch jobs complete successfully and on time
What is our primary use case?
My main use case for MarkLogic involves running queries to check some of the jobs. I run batch jobs and then I want to check whether the batch jobs are running fine. I check the data on MarkLogic by running the query on the query logic portal.
Regarding my main use case with MarkLogic, I find it very handy because every time I run a job, I go and run the query. I go to different databases and then see whether it's running fine. It is enjoyable working with MarkLogic.
A recent task where MarkLogic was especially helpful involved trying to check the number of batch jobs, DES or PDM jobs, and different jobs. We always check the number and then based on the number, we compare with other tools and then see whether it's matching. It is a comparison with multiple tools. If, for example, PG Admin was not working with PostgreSQL, but MarkLogic was working fine, we were able to fix the issue on the other tools which were not working.
What is most valuable?
In my opinion, the best features MarkLogic offers are that it is very easy to use and has a very fast response time.
The fast response time and ease of use help me in my daily work because it is really helpful since we have to run a lot of jobs at the same time and then we want to make sure everything is running as expected. It always helps us to check whether our jobs are running fine.
MarkLogic has positively impacted my organization as I think company-wise, it is one of the go-to tools for validating the jobs we are running. It is very helpful for us to deliver our products with quality and on time.
Using MarkLogic has resulted in specific outcomes, as we run jobs for a long time, sometimes for a couple of days, sometimes for ten hours or twelve hours. It helps us a lot.
What needs improvement?
I would say the features can be improved, as maybe the UI could be a little better. I am not sure if there are other options, but the one I am using is from the query console, so maybe I am not aware of other UI dashboards.
There are ways MarkLogic can be improved. I would like to add that a better UI with more features on it, something user-friendly, would be beneficial.
I think there is nothing else that could be improved about MarkLogic.
For how long have I used the solution?
I have been using MarkLogic for two years.
What other advice do I have?
If someone is looking into using MarkLogic, I would say MarkLogic is very helpful for providing the monitoring with detailed features. Running the query is very easy. I rate this product an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Mar 27, 2026
Flag as inappropriateBuyer's Guide
Download our free MarkLogic Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2026
Product Categories
NoSQL DatabasesPopular Comparisons
MongoDB Enterprise Advanced
Microsoft Azure Cosmos DB
Cassandra
Cloudera Distribution for Hadoop
Neo4j Graph Database
DataStax Enterprise
CouchDB
Buyer's Guide
Download our free MarkLogic Report and get advice and tips from experienced pros
sharing their opinions.








