Tag: MarkLogic

Rebalancing in MarkLogic redistributes content in a database so that the forests that make up the database each have a similar number of documents. Spreading documents evenly across forests lets you take better advantage of concurrency among hosts.

A key feature of MarkLogic is ACID compliance. ACID stands for atomicity, consistency, isolation, and durability, and meeting these four requirements means that transactions in MarkLogic are reliable.

“For retailers who lack the capability of using information about their card-holding customers and turning this data into tailor-made, individual, shopper-specific propositions – loyalty systems are no more than an expensive gadget.” 1 In my last post, Reinventing Loyalty Programs to Win, we discussed the fact that most loyalty programs in retail fail because they lack vision or […]

Aggregates like count and sum are heavily used in RDBMS. For people learning MarkLogic, the first match for the same set of functions (fn:count, cts:count, fn:sum, cts:sum) are generally not the right choice. Let’s take a look at their lexicon-driven counterparts.

This is the first in a series of three blogs discussing David Gorbet’s “Shape Da Future” keynote address at MarkLogic World 2015. The data word has changed. Data itself is now a commodity, but the technology used to create experiences with it is not. New database technology can now drive tailored, real-time experiences that would’ve […]