We Know MarKLOGIC
OverStory has a proud MarkLogic pedigree like no other consultancy. We are MarkLogic Partners, and Senior OverStory technology staff helped build MarkLogic itself, working closely with the MarkLogic founders for several years. Beyond that, we have ex-Marklogic staff in several teams, and treat this system as a core strength.
However, if you don't have a MarkLogic license, we can suggest and use appropriate systems that fit your budget and needs.
MarkLogic developer certification
Our engineers have many years of experience working for MarkLogic or with MarkLogic systems in various situations. This experience is massively valuable, however the certification is important for clients to see we have attained that level.
We have some staff members with Developer certification already, and will be moving more staff through this certification very soon.
There are many flavors of NoSQL database available, but not all are document-oriented. Native document storage and indexing can be vital to effectively manage disparate data that clients often need. MarkLogic stores documents that are structured as XML and natively uses the XML Data Model (XDM) internally. The richness of the XDM provides many benefits over more simplistic data models like key-value or JSON/BSON, especially for mixed textual content.
In addition to the rich content model for managing textual content like reports and other written material, MarkLogic is unique in that it also incorporates a high performance search engine and an RDF triple store, all in one transactionally consistent, structure-aware index system.
The first two features are essential for handling content in conventional ways, such as searching, sorting and faceting, while the third is a prerequisite for analytic “big data” processing.
While it is possible to build a system with these capabilities using individual point products, it is far more difficult and time consuming (and thus more expensive) to build. Also the integration and synchronization requirements are far more complex and error prone.
This allows all MarkLogic-specific code to be neatly encapsulated within MarkLogic itself, providing clean separation of concerns from other tiers of the application stack so that there are no external dependencies on MarkLogic and no “abstraction leakage”.
Contact us for help with MarkLogic.