OpenDQ vs Yugandhar Open MDM Hub

OpenDQ is an open-source product for data quality across structured and unstructured data, listed at zero license cost. Its tools include profiling, standardization, fuzzy matching, deduplication, validation, reporting, and monitoring. The maker says its profiling framework can scale from millions to billions of records. Machine-learning components parse free-form text into components, and enrichment can add demographic, geographic, business, and consumer data. External enrichment is optional and subscription based. The technology page describes Apache Spark-based clusters for compute-intensive processing. The maker also says OpenDQ synchronizes data in real time with over 200 applications and supplies connectors for popular data systems. Platforms include API, self-hosted, and web. For its MDM platform, listed deployment choices are cloud, hybrid, and on-premise, with SOA/REST APIs and role-based data-level and domain-level access. The company describes auditing and data lineage for its securities master solution. Infosolve Technologies says it serves organizations from nonprofits to Fortune 100 companies and was founded in South Brunswick, New Jersey, in 2003; its headquarters are in Princeton, New Jersey.

Yugandhar Open MDM Hub is a free, Apache 2.0-licensed project for integrating and harmonizing customer master data. Its extendable model covers people, organizations, accounts, addresses, phone numbers, identifiers, relationships, vehicles, preferences, and properties. The project describes more than 450 prebuilt services, including 50+ composite services and 400 base table services. It offers REST and message-queue interfaces, with embedded validations, business rules, and match-and-merge capabilities for data quality.

MariaDB and Oracle are preconfigured, with extension options for MySQL, DB2, NoSQL, and PostgreSQL. Listed components and integrations include ActiveMQ, JTA, ORM, Spring Boot, Hibernate, JBoss, and Maven. User- and role-based authorization and row-level audit history support access control and transaction tracking. Other features include multilingual reference data, event management, paginated retrieval and search, and JSR 107-compliant Ehcache caching. Deployment options include an embedded Spring Boot web server such as Tomcat or a JEE container such as Red Hat JBoss. Production hosting supports most Linux distributions; CentOS and Ubuntu are listed as tested. Requirements include Java JDK 1.8 and MariaDB 10.3 or later or Oracle.