MarkLogic World 2020 Live Keynote – Register Now

All Posts By

Damon Feldman

Damon is a passionate “Mark-Logician,” having been with the company for over 7 years as it has evolved into the company it is today. He has worked on or led some of the largest MarkLogic projects for customers ranging from the US Intelligence Community to HealthCare.gov to private insurance companies.

Prior to joining MarkLogic, Damon held positions spanning product development for multiple startups, founding of one startup, consulting for a semantic technology company, and leading the architecture for the IMSMA humanitarian landmine remediation and tracking system.

He holds a BA in Mathematics from the University of Chicago and a Ph.D. in Computer Science from Tulane University.

July 24, 2019
MarkLogicデザインパターンは、MarkLogicアプリケーションの設計における一般的な問題に対処するための、再利用可能なソリューションです。
Two emerging technology patterns help make combined, enterprise-wide data useful and secure: data fabrics and Operational Data Hubs (ODHs). This blog outlines the differences between data fabrics and data hubs, and outlines how they best work together.
Data Lakes have been too flexible. Federation has been too rigid. It all has to do with the Movement, Harmonization and Indexing of data. But wait there is another approach -- the Data Hub is just right.
MarkLogic design patterns are reusable solutions for many of the commonly occurring problems encountered when designing MarkLogic applications.
データレイクは柔軟性が高すぎる。フェデレーションは柔軟性に欠ける。それはすべて、データの移動、調整、インデックス付けに関係します。でも、別のアプローチがあります。データハブなら、すべてご希望どおりです。
They had data in multiple data stores -- and wanted Polyglot persistence but got poly lot of headaches instead. Then they switched to MarkLogic's multi-model database.
We all have an Uncle Mort – that pragmatic, no bull, calls-it-like-he-sees-it type of guy. Today, I’m going to divulge a secret about how to figure out if you need a document database or not. I’ll start with some technical background, and then we will have a sit down with Uncle Mort! Let’s just review a […]
A few weeks ago, I blogged about Data as a Service – “DaaS” – what it is, pitfalls and why it is valuable. Today I’m following that up with strategies and techniques for getting it right. My summary from the previous blog post I defined DaaS as an architectural pattern where your most valuable services […]
Learn about what Data as a Service (DaaS) is and what benefits it is supposed to provide.
This website uses cookies.

By continuing to use this website you are giving consent to cookies being used in accordance with the MarkLogic Privacy Statement.