The new website for MarkLogic is Visit it.


Everything From Data Tips and NoSQL Best Practices to Industry Specific Insights

Tips on what to look for when choosing an enterprise search solution, and on developing your solution so it meets the unique needs of your organization.
Your application is live in production, you have millions of documents, and now you want to change a database setting or add a custom index. You know that when you move these changes to production it’s going to take hours, maybe days to re-index all the affected documents and while MarkLogic is re-indexing it’s going to take up resources. You need a solution to mitigate the impact of Re-indexing.
Discover the top 7 reasons for using a range index in MarkLogic.
Are there any recommendation regarding the stemming option to use between basic, advanced and decompounding? Would it be a good approach to always use the "advanced" option when enabling stemming for French?
How many is too many range indexes? Will I ever need 10,000 range indexes?
Generally, optimizations in the evaluator try to be lazy whenever they can when evaluating functions. This allows the application to process data only when needed and limits memory use to only what is needed. But sometimes, you need to evaluate eagerly to improve performance. Here we discuss one use case when it is best to specify eager evaluation.
Recently, I built a MarkLogic web application using a lot of XSLT and a dash of XQuery. I was able to apply my understanding about how to optimize code to make a site like this perform better, so I thought I would share some of these insights with other beginners. Whenever MarkLogic evaluates an XPath […]