This is a brief post I've been wanting to write for sometime now. It's a post I alluded to when I started the MarkLogic: Beyond NoSQL series earlier this year.
We're making good on an earlier promise to explain our architetcure, in more detail. Beyond simply saying what our customers already know (e.g. things like, "MarkLogic is really fast"), we've taken the time and effort to explain why and how this is so.
Specifically, MarkLogic Principal Technologist, Jason Hunter, has published Inside MarkLogic Server. This paper provides a deep dive into our architecture and data model so that you can understand "what's under the hood" and how best to use it.
As Jason told me, his hope is that, after reading this paper, you'll have the knowledge to do things like predict how long a given query should really take in your environment - should it happen in 200ms? Or in 5ms? How many times will it hit the disk? And so on. Likewise, you'll be able to make better informed application design and deployment.
If you want to understand what's inside MarkLogic, this paper is for you. Enjoy!