Blog(RSS)

Keeping Reputation Consistent

by Kasey Alderete
In designing Samplestack, a sample MarkLogic application that provides search and updates across Question & Answer content, our team wanted to demonstrate how the database’s built-in capabilities enhance the application developer’s experience. One of the differentiating features of MarkLogic’s enterprise NoSQL database is having ACID transactions, and more specifically its support for multi-document, multi-statement transactions.  It was a no-brainer that we would look for ways to meet requirements and keep the data consistent through the use of transactions where appropriate. Once we defined the application requirements, we ended up with a scenario that required the database to successfully execute multi-statement transactions. When an answer is selected as the ‘accepted’ answer, parallel updates are required for the content and the user(s): Update the answer to indicate its status as ‘accepted’Increase the reputation of the user with the ‘accepted’ answerDecrease the reputation of th ...

By the way, MLCP just got better

by Dave Cassel
With all the great stuff in MarkLogic 8, you might have missed these changes in MLCP.

Node.js and Express.js sessions using MarkLogic 8

by Matt Pileggi
Quick start for enabling MarkLogic 8 Session Stores with NodeJS and Express

An Exploration into Android Gaming, Powered by MarkLogic

by Brent Perry
Last year before I joined MarkLogic, I took it on myself to start the development of an Android-based geo-location game that we’ll call “Contagion”. I had ideas for how it would work, the game design, and all kinds of areas to expand if it were successful. There are many technical challenges to overcome with this kind of project, though. In a matter of days a successful title on Google Play can go from a few users to a few hundred thousand users. Additionally, based on user feedback I would need to modify the software frequently to add features and possibly modify game design elements. All of this added up to some traditionally nasty software requirements: a technical stack with high scalability and flexibility. Coming from a software background in enterprise java development, my instincts were to go for a classic 3-tiered architecture. The game’s business logic would live in a DropWizard (Jetty, Jersey, Jackson for HTTP, REST, and JSON handling respectively) layer running as a standoff se ...

A UDF for Ranged Buckets

by Dave Cassel
A UDF provided some advantage over a simple custom constraint

blogroll Blogroll