MarkLogic’s triple store allows us to use custom inferencing rules, consumer profiles and dynamic behavior to build a simple, foundational, semantic recommendation engine.
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.
A car without effective brakes might be good for the drag strip, it isn’t good for driving your kids around. Is speed any reason to have a database that doesn’t provide transactions?
Amazon has upended the traditional brick and mortar way of storage and retrieval — with its “chaotic storage.” Can this inspire how companies store, organize and retrieve data?