4 out of 5.0, Reviewed Aug 31, 2016
The sales and technical teams were knowledgeable and responsive.
Purchase training from provider.
Stability and reliability.
Am satisfied with our experience.
Am comfortable with the technology and implementation strategy used.
Knowledgeable sales and technical support when needed.
5 out of 5.0, Reviewed Aug 10, 2016
MarkLogic has worked very well for us. We are able to load large amounts of data very quickly and make that data available to products and the business very quickly speeding up the time to market for our products. MarkLogic has also given us the ability to analyze and search the data very easily without having to invest a lot of time and effort in building the tools necessary to do the analysis. It also has several enterprise features built in which helps in the maintenance and operations of our IT environment. In short, MarkLogic has helped us focus on the business value without spending too much time on making the technology work to derive the said business value.
I would ask prospective customers to keep an open mind when evaluating MarkLogic. Other open source products that compete with MarkLogic may seem cheaper or may seem better at one aspect but if you dig deeper you would see that no other product has the breadth and depth of enterprise features that MarkLogic has.
The fact that indexing happens at load time which enables searches to be performed soon after loading the data is what I like the most. There is no need to do the extensive data modeling upfront.
I don't have anything that I dislike about MarkLogic.
I wish they market MarkLogic more aggressively.
We wouldn't do anything differently if we were to start over.
MarkLogic has been very responsive in their customer service and support.
5 out of 5.0, Reviewed Aug 9, 2016
MarkLogic provides the best performance, and price/performance point, for content management for my organization. We leverage MarkLogic across our enterprise, including workflow management and as a central internal content staging hub, for content ranging from small XML to large binary content. Our production core data hub persists over 40TB of content, in a cluster of 60+ hosts, with our inbound and outbound processing for over 170 collections all running within that cluster. The ML integrated application and database environment reduces my overall hardware costs while simplifying administration and management, compared to our RDBMS and traditional service bus architectures. For our core content management, MarkLogic exceeded expectations for performance and time-to-delivery. We implemented in days multiple aggregation workflows in MarkLogic Server that would have required many weeks on alternate platforms; I do more, more rapidly and with fewer developers, with MarkLogic. MarkLogic Server is scalable and stable; my operational DBA requirements are less than our 'traditional' RDBMS platforms, and over 7 years of use across our enterprise generates fewer calls than our other DBMS platforms. My team manages several RDBMS and NoSQL products, and MarkLogic reduces my overall cost of ownership, particularly when considering the costs of managing container/application server components. Leveraging MarkLogic as a data hub greatly benefits our content quality and product QA validation. Where my other DBMS implementations tend to limit useful queries to a few (or 1) indexed elements, our testers and data stewards with MarkLogic stores are generally able to query any node/element/value for any collection, and do so across multiple collections concurrently.
Understand your application(s) and requirements with respect to both the application stack and data persistence, and apply the best fitting technologies/platforms to your solution; for my core internal applications MarkLogic fits well, but we still do new development with other platforms, where other platforms make more sense or cost less. MarkLogic serves my enterprise well and facilitates doing more with less. I find it an amazingly flexible and useful platform. Our content mapping and integration workflows are an excellent fit, it is truly a best of class enterprise database platform, and I've found no other platform more useful when supporting rapid development of content-flow or web-services applications. My data governance and testing efforts are much enhanced by MarkLogic and its excellent and intuitive interactive query facilities. That said, I still have new development on other platforms, where those technologies and platforms make more business and/or financial sense. We leverage a Hadoop ecosystem for online product content processing, and though we load this compiled content to MarkLogic for validation, Hadoop has a critical place in our enterprise alongside MarkLogic. Some of our custom workflow systems are likewise using RDBMS and/or key-value stores, often driven by component reuse or business cases not requiring intensive server-side processing. While there are a couple of systems I hope we can soon refactor to MarkLogic, and MarkLogic is a critical part of our enterprise, yet business realities still sometimes drive us to leverage other technologies and platforms. I continue to find new applications for MarkLogic, but the bottom line uses the right tools for the job and the business.
MarkLogic Server provides a scalable clustered environment, having solid enterprise-class operations features including incremental backups; with all of the management and administration benefits plus rapid application development and content management features, I get more done with fewer staff with MarkLogic. For me that is a key differentiator with MarkLogic - my developers can develop better applications more rapidly, my QA and data validation staff does better work in less time, and my administrators can support large-scale MarkLogic and still have time and attention to attend to our RDBMS platforms. MarkLogic improved our software deployments by allowing us to retire separate application server containers, and for rapid prototyping of content processing or information delivery I've not used a better platform. Developers tend to get up-to-speed quickly, and with our complex schemas have tools to effect our transformations and mappings promptly. We still do modular development, but in an easier to manage container and a set of APIs that allow us to pick the right language/environment for the task.
If I had answered this a couple of years ago, it would have been a relative lack of a mature REST interface; MarkLogic now provides a robust REST API. Our organization is still refactoring utilities to use the REST interface from the xQuery API, though that is a minor set of additional tasks and we are doing this for our ongoing convenience and not any issues with the existing API. So, no major dislikes, although it could use a few tweaks to the administrative console GUI and granularity of user-administration security.
My team would appreciate having a native user administration facility not centered on a DBA-centric administrator role; we currently have DBAs performing routine user administration, because - unless we develop and maintain our own user administration interface - our help desk would have permissions/privileges outside the currently defined help desk role. In short, it would help my DBA team to have a user-administrator role we can assign to a help desk that only permits user modifications. We currently maintain a proxy interface that works to enforce this separation but requires my team maintain it. I suppose that with my team running MarkLogic on about 250 hosts, for thousands of databases and application servers, and a production aggregate of over 100TB of content, with a team of only 4 DBAs, this minor suggestion on user management being what I hope the vendor did differently speak to how solid, stable, and useful MarkLogic is to our enterprise.
Implement some of our current Java/JEE service bus with message queuing applications, based on RDBMS platforms, using MarkLogic Server. My ingestion and aggregation/mapping workflows can be much faster with fewer resources, in a much easier to manage and administer package, with MarkLogic. I would really have liked to evaluate Semantics much earlier in our product and business management architecture decisions; there is some great business fits for Semantics where we adapted or developed our own parts of the solutions in the content pipeline and customer management.
Truly the most performant platform for much of what we do. Enterprise-level operations facilities and very easy to scale on-demand. We could do everything we do on other platforms, but MarkLogic hits our time-to-production, uptime, scaling, development costs, and operational costs targets better than any other platform we've used for spoke-and-hub internal content delivery and curation.
Excellent engineering and sales support!
Out of the box, it works for most applications and uses scenarios; the design is straightforward, implementation likewise, and the platform lends itself to scripting and automation. Performance and tuning are relatively easy and straightforward. Scaling is relatively simple to implement and maintain, and we modularize and script most of our administrative and cluster management functions. Compared to some competing products, MarkLogic has a very low cost to administration and management, particularly in tuning app servers and very large databases.
5 out of 5.0, Reviewed Aug 9, 2016
Worked on site with vendor resources. Resources were experienced and provided great value.
Ensure that team resources are dedecated to project and available from the start
Should provide a foundational effort for future projects.
Nothing to note yet
Our company should have completed more preparation up front including the finalization of requirements and modelling.
5 out of 5.0, Reviewed Aug 9, 2016
MarkLogic spent a lot of time working with our company to help us explore and evaluate why their product was different from others in this space. They completed multiple POC's and provided insight into how their product could fit into our architecture.
Knowing your architecture direction, and all the spaces in which this product fits is imperative. You need to not only look at the investment from a database management solution or a data warehouse solution but from a holistic perspective in alignment with your architecture goals.
I love that this product has such flexibility, and it fits into multiple spaces in our architecture. We are
3 out of 5.0, Reviewed Aug 9, 2016
Besides schema flexibility and scalability quite impressed with Enterprise features provided by MarkLogic
5 out of 5.0, Reviewed Aug 8, 2016
I work as a DBA and admin UI was clear to follow and assists the Admins in really good way. The Administration Guide helps a lot improving the performance of the server.
Easy to implement and setup
Adding Best practices in Documentation would help users a lot.
We use proxy for deployment and we never faced trouble with it.
4 out of 5.0, Reviewed Aug 8, 2016
Marklogic has been good for our application, which relies heavily on Marklogic's NoSQL capabilities and ability to natively process and search XML documents. It has also been easy to scale marklogic as our customer base grew.
Wasn't directly involved in this
5 out of 5.0, Reviewed Aug 3, 2016
We purchased MarkLogic licenses several years ago but due to corporate constraints did not, at that time, train our development team in its capabilities or exploit its features. A change in our corporate structure presented an opportunity to deepen our investment and to use MarkLogic as the foundation for a re-architected and redesigned web application. We trained our development team, invested in a MarkLogic consultant who guided our implementation, and also deployed a user-centered design process to guide requirements for the new site. We recently successfully launched the new application to our customer base. MarkLogic's search capabilities are a key component of the new design, and the resulting improvements to the customer experience are driving a record number of new sales. Our internal and external stakeholders are extremely pleased with the results. The project spanned about 12 months, although the bulk of the development effort was focused over half that time. The project required investment because our investment in MarkLogic had languished (in 2015 we were still running version 4; we are now on version 8), but the overall investment definitely paid off. The flexibility of NoSQL was extremely beneficial throughout the development process, and we're considering other ways to leverage the work we've just delivered.
Don't forget that technical capabilities alone will not make a customer-facing solution successful; you must also invest in the user experience. Create user profiles, perform competitive analysis, and build a front end that optimizes for the most important use cases. It was very helpful for the MarkLogic consultant to be able to understand the use cases that were most important for our customers to perform easily and successfully.
It's very clear to us that MarkLogic is invested in our success. Account management is ably performed.
We wish that the annual MarkLogic conference had been closer to us; for budget reasons we had to constrain the number of attendees who could participate.
We underestimated the ease of implementing search capabilities. In hindsight we should have allocated more time for understanding how to structure our data and queries so that we could get quick performance when searching documents and retrievingsearch results with previews for each result.
As is typical with so many development projects, competing development priorities and critical escalations reduced the availability of our internal development team to shadow the MarkLogic consultant who jump-started our implementation. Ideally, it would have been better if our internal resources had more availability to work side-by-side with the MarkLogic resource from the beginning.
Our investment at this time is focused especially on the advantages of NoSQL and MarkLogic's ability to support an application that is focused on searching for and viewing documents and other media types, especially with data that is not particularly well structured. We are satisfied in this area, and I am less equipped to rate its other capabilities.
5 out of 5.0, Reviewed Aug 2, 2016
Unwrapping our brains around a operational database that isn't relational was the first challenge. When someone says, "We can start building the application and worry about the data model later.", you meet it with a suspicious eye. But the fact is, that this platform has allowed us to tackle problems we might not have even evaluated before because of the complexity of doing this in a relational model. Lastly, we saw results very quickly because so many of the features are built into the platform (ACID, Search, Security, Scalability) we didn't have to think through strapping on other vendors add-ons to achieve these needs.
Spend some serious time thinking through as much as you can and lining up the sales process and licensing requirements up front. I would also make sure the resourcing plan of training internal developers and using vendor Prof Services is well thought out. We ended up relying on many more internal features of MarkLogic that I thought we might build into the Application Layer. All positive in the long run, but resourcing at some points is/was challenging.
The built in components like Search, ACID, scalability, etc. Don't need to think about a lot of that stuff.
The search is very fast and I can't say this with total confidence, but it appears that adding/removing indexes is like any other system, time consuming. This is kind of a cake and eat it too.
Published Pricing for customers. I also think they need better marketing to explain the 'how' of MarkLogic. They struggle with this as well. I talked to perspective customers and their decision point was when they were showed MarkLogic. The all had problems they couldn't solve in relational models and within 24-48 hrs. had working POCs to show what is possible.
I think that we might have looked at the built in Semantics engine earlier as I think it might have changed the way we arechitected. I think we might have seen some results even earlier and given us a little more flexibility when it comes to faceted search as well, how we approach ETL(we now are allowed to effectively do ELT), and how we think about enriching data with public and private information like Triple Stores.
Previous comments illustrate large number of built in functionality that are mostly Enterprise features.