TrustRadius Insights for MarkLogic Server are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
MarkLogic is a versatile software used by various industries to implement solutions for their clients. It is utilized in publishing workflows, enterprise search, big data analytics, and the semantic web. Users have praised its powerful geospatial search feature, which efficiently searches locations based on latitude and longitude. MarkLogic's indexing and tokenization techniques contribute to the quick execution of search queries.
Healthcare organizations rely on MarkLogic as a backend store for patient records, enabling storage, retrieval, and updates. By using a micro-services approach with patient matching and search functionality, MarkLogic helps keep patients up-to-date across multiple hospitals. It also serves as a central store for companies dealing with large amounts of data across multiple clusters, providing efficient storage and search capabilities.
In the academic publishing field, MarkLogic is extensively used for end-to-end data flow, including metadata and full-text content. Its newer features like semantics and JavaScript support are leveraged to develop cutting-edge technology.
MarkLogic's multi-model approach, scalability, and exceptional performance in handling XML data make it a preferred choice. It is also employed for reporting purposes with potential for future OLTP and OLAP services. Companies utilize MarkLogic to create DataHubs that consolidate data from various sources, enabling business teams to leverage the data with BI tools.
The technology department at Zynx Health relies on MarkLogic as the primary database layer for clinical decision support analytics. MarkLogic's XML-based solution proves valuable in handling hierarchically structured and semi-structured healthcare data.
MarkLogic is an enterprise NoSQL database server which has multi-model approach, is highly scalable and with exceptional performance. We identified MarkLogic as the best fit because they can load all the data in XML format through different silos and as MarkLogic provides real time services through its RESTful services it can be used as both OLTP and OLAP servers. As of now it is being used only for reporting purposes. We are creating DataHub for our client's various applications serving different portfolios which connect to multiple isolated data silos. Our objective is to bring all that data to DataHub and to create DataMart process for the business team to make use of this data using BI tools. We are using the MarkLogic DataHub Framework which creates documents in a specific envelope pattern. This framework will have set of plugins inside which our code and configurations files will be present.
Pros
MarkLogic is highly scalable and with exceptional performance.
Marklogic provides real time services through its RESTful services it can be used as both OLTP and OLAP servers.
MarkLogic is identified as the best fit because they can load all the data in XML format through different silos.
Cons
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.
Likelihood to Recommend
MarkLogic is very well suited for all XML and JSON files to get loaded and to derive insights from those huge data sets. It is less appropriate when the number of files is directly proportional to run the query, which should be taken into consideration.
We are searching some restaurants near by any location. We have used the geospatial search feature of MarkLogic. For those who do not know what geopspatial search is the next 3 line is for you. Its search based on geo location using latitude and longitude as parameters. The whole world is divided into some grids by latitude and longitude. Using that feature each and every location can be presented by 2 numbers, one how far and in which direction is it from 00 degree latitude and from 00 longitude. Geospatial search is one of the great features of MarkLogic. It has some in-built features to calculate the distance of a data point from another data point provided that both data have latitude and longitude data present in it. Another features which I like about MarkLogic is - It is really efficient for searching. The time it takes for a search query to run is really less. Thanks to the Indexing and tokenization technique of ML.
Pros
MarkLogic supports fully ACID transaction and I think this is very rare in a NoSQL system.
The recent version of MarkLogic has Integration with Node.js, REST, JSON which has really made the developers life easier to build integrated systems.
MarkLogic provides superb documentation for us. It really helps to understand which features work how. Example is- the whole dedicated website for it. https://docs.marklogic.com/
From the point of infrastructure - Installation, configuration and deployment is very fast. Compared to RDBMS , it's really easy to scale MarkLogic horizontally by adding nodes.
Cons
The licence cost is HIGH.
The amount of space required to store the data seems high hence costly.
The compatibility with legacy system is not yet available. I feel this area needs to be improved very fast.
Likelihood to Recommend
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.