Welcome!

Microservices Expo Authors: Elizabeth White, Carmen Gonzalez, Pat Romanski, Liz McMillan, Sematext Blog

Related Topics: Microservices Expo

Microservices Expo: Article

Master Data Management Meets SOA

A symbiotic relationship

Master Data Management (MDM) is often defined as "management of master data (customer, product, supplier, etc.) that is shared across disparate IT systems and groups." However, this simplistic description doesn't do justice to the complexity of the MDM's task and problem area. Master Data Management encompasses areas such as Customer Data Integration (CDI), Product Information Management (PIM), and Global Data Synchronization Network (GDSN); and partially overlaps the areas of Identity Management System (IdM), Business Intelligence systems, data quality, and data integration. This broad area of potential application causes multiple perspectives, diversity of stakeholders, and a fair amount of confusion across clients investigating an MDM solution.

The business need for MDM is made manifest both implicitly and explicitly. Its utility tends to be obvious in efforts around conformance and auditing, accurate reporting efforts, and a single view of the customer initiatives. However, MDM is often also a hidden requirement for successful consolidation projects after mergers and acquisitions. Its value in terms of return on investment, cost savings (reduced storage, reduced analysis, development, and maintenance, etc.), increased revenue (consistent view master data, reduced time to resolution, and effective decision making), and competitive advantage (operational efficiency, improved visibility to company performance, etc.) has been well documented by multiple reputable groups and authors (AMR Research, Forrester Research, Gartner, and the Yankee Group) so we won't explore the existing benefits that the reader can easily reference. We will however discuss the benefits of MDM as they relate to SOA enablement.

MDM systems can be "federated," "integrated," or "hybrid" reflecting a combination of the first two fundamental architectures. These three types of system characteristics are as:

  • Federated MDM - cross references key identifying information from participating systems to implement a registry-style solution. The main benefit of a federated solution is non-intrusiveness on participating systems that maintain their original context.
  • Integrated MDM - stores all master data information from all participating systems in a centralized MDM repository. This centralized repository houses the "gold copy" of all master data information. The main benefit of the integrated approach is that it provides the most complete, accurate, and consistent single view of master data.
  • Hybrid MDM - stores common data elements from participating systems creating a "light gold copy" of the master data, while disparate elements are referenced from their original system of record. The benefit and drawback of the hybrid solution is the partial combination of the federated and integrated benefits.
Service Oriented Architecture (SOA)
From a systems design perspective, SOA is an architectural approach based on distributed computing principles. SOA has numerous other aspects in topics as diverse as business process design and IT governance. However, these aspects go beyond our scope here.

As an architectural paradigm, the participating components of a SOA system include: service providers, service consumers, intermediary services, and registries. A service provider publishes a service in the registry to be consumed by a service consumer who can identify the interface, purpose, and location of the service from the registry. Intermediary services intercept and handle operations that are common across services and can be leveraged instead of recreated every time. Typical intermediary services include: authentication, auditing, logging, monitoring, and message routing. All communications are done through commonly agreed on standards (UDDI, SOAP, WSDL, XML, HTTP/SSL). The design principles governing SOA are primarily object-oriented paradigms extended to address the service-oriented requirements. These service design principles include: loose coupling, service contract, abstraction, composability, autonomy, reusability, statelessness, and discoverability.

Services access information from a data services layer. A data services layer provides an abstraction layer between producers and consumers of data. The data services layer presents consumers with a virtual aggregated view of data from multiple data sources in a consistent and centralized fashion. The layer's interface supports all consumers (human, application, external parties, or business services) while providing agility to data source providers.

A data service layer offers many benefits. Consumers are insulated from complexity, location, and changes in source data systems through abstraction. Providers have the flexibility to change underlying data schemas without impacting consumers through abstraction. Companies can centrally manage, monitor, measure, and report on the enterprise view of the data and metadata.

The three main categorizations of services in the data services layer are: Enterprise Data Services, Enterprise Metadata Services, and Enterprise Data Platform Services.

  • The Enterprise Data Services area encompasses all the services around the data. For example, a request to be addressed by this area would be: Retrieve "gold copy" of "customer A" record.
  • The Enterprise Metadata Services area includes all the services around the metadata. This area would address items such as: Retrieve master data schema of "customer A" record.
  • The Enterprise Data Platform Services area supports all the services around the platform including management, monitoring, and reporting. An example of a request here would be: Retrieve MDM system, quality of service targets.
Services are defined in each area based on function (examples are shown in Figure 1). In each service and across all three areas, methods for search, access, create, update, delete, manage, monitor, and reporting functionality should be evaluated for applicability and realization.

MDM Meets SOA
MDM and SOA evolved separately but share many design principles.

  • "Contract first" applies to the interfaces in MDM and the service definition in SOA
  • "Reusability" applies to data through conformance in MDM and services through SOA principles in SOA
  • "Discoverability" applies to data through the master data repository in MDM and services through registry in SOA
  • "Abstraction" applies to source system complexity and MDM and underlying service complexity under SOA.
MDM, however, typically doesn't embrace SOA's "loose coupling" principle. Extending MDM with loose coupling allows support for SOA's semantic conformance needs.

As MDM practitioners contemplating supporting today's SOA systems, we need to become familiar with SOA standards and strive for loose coupling with external systems. Eliminating point-to-point interfaces and replacing them with service-enabled integration minimizes the impact of changes from integration partners and consumers. Loose coupling should be applied internally as well to create an agile MDM system. An agile service-oriented MDM system provides its data quality, conformance, and other MDM functionality as business or data "services" available for net-enabled consumption by external parties. Finally, MDM systems should be able to handle the extensible data types (XML, HTML, PDF, and e-mail) common to net-centric application and be able to expose the master data model as part of the enterprise canonical data model (CDM) for service consumption.

More Stories By John Kalogirou

John Kalogirou is MomentumSI's information management director. He has 15 years of experience in managerial and technical roles guiding SMBs and Fortune 500 companies to implement information, integration and intelligence solutions toward improved business effectiveness and profitability.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
Between 2005 and 2020, data volumes will grow by a factor of 300 – enough data to stack CDs from the earth to the moon 162 times. This has come to be known as the ‘big data’ phenomenon. Unfortunately, traditional approaches to handling, storing and analyzing data aren’t adequate at this scale: they’re too costly, slow and physically cumbersome to keep up. Fortunately, in response a new breed of technology has emerged that is cheaper, faster and more scalable. Yet, in meeting these new needs they...
@DevOpsSummit taking place June 6-8, 2017 at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @DevOpsSummit at Cloud Expo New York Call for Papers is now open.
In his session at 19th Cloud Expo, Claude Remillard, Principal Program Manager in Developer Division at Microsoft, contrasted how his team used config as code and immutable patterns for continuous delivery of microservices and apps to the cloud. He showed how the immutable patterns helps developers do away with most of the complexity of config as code-enabling scenarios such as rollback, zero downtime upgrades with far greater simplicity. He also demoed building immutable pipelines in the cloud ...
Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more business becomes digital the more stakeholders are interested in this data including how it relates to business. Some of these people have never used a monitoring tool before. They have a question on their mind like “How is my application doing” but no id...
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
Information technology is an industry that has always experienced change, and the dramatic change sweeping across the industry today could not be truthfully described as the first time we've seen such widespread change impacting customer investments. However, the rate of the change, and the potential outcomes from today's digital transformation has the distinct potential to separate the industry into two camps: Organizations that see the change coming, embrace it, and successful leverage it; and...
Monitoring of Docker environments is challenging. Why? Because each container typically runs a single process, has its own environment, utilizes virtual networks, or has various methods of managing storage. Traditional monitoring solutions take metrics from each server and applications they run. These servers and applications running on them are typically very static, with very long uptimes. Docker deployments are different: a set of containers may run many applications, all sharing the resource...
Join Impiger for their featured webinar: ‘Cloud Computing: A Roadmap to Modern Software Delivery’ on November 10, 2016, at 12:00 pm CST. Very few companies have not experienced some impact to their IT delivery due to the evolution of cloud computing. This webinar is not about deciding whether you should entertain moving some or all of your IT to the cloud, but rather, a detailed look under the hood to help IT professionals understand how cloud adoption has evolved and what trends will impact th...
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his session at @DevOpsSummit 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, showed how customers are able to achieve a level of transparency that enables everyone fro...
Internet of @ThingsExpo, taking place June 6-8, 2017 at the Javits Center in New York City, New York, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @ThingsExpo New York Call for Papers is now open.
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
You have great SaaS business app ideas. You want to turn your idea quickly into a functional and engaging proof of concept. You need to be able to modify it to meet customers' needs, and you need to deliver a complete and secure SaaS application. How could you achieve all the above and yet avoid unforeseen IT requirements that add unnecessary cost and complexity? You also want your app to be responsive in any device at any time. In his session at 19th Cloud Expo, Mark Allen, General Manager of...
"Dice has been around for the last 20 years. We have been helping tech professionals find new jobs and career opportunities," explained Manish Dixit, VP of Product and Engineering at Dice, in this SYS-CON.tv interview at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Application transformation and DevOps practices are two sides of the same coin. Enterprises that want to capture value faster, need to deliver value faster – time value of money principle. To do that enterprises need to build cloud-native apps as microservices by empowering teams to build, ship, and run in production. In his session at @DevOpsSummit at 19th Cloud Expo, Neil Gehani, senior product manager at HPE, discussed what every business should plan for how to structure their teams to delive...
Rapid innovation, changing business landscapes, and new IT demands force businesses to make changes quickly. In the eyes of many, containers are at the brink of becoming a pervasive technology in enterprise IT to accelerate application delivery. In this presentation, attendees learned about the: The transformation of IT to a DevOps, microservices, and container-based architecture What are containers and how DevOps practices can operate in a container-based environment A demonstration of how ...
As we enter the final week before the 19th International Cloud Expo | @ThingsExpo in Santa Clara, CA, it's time for me to reflect on six big topics that will be important during the show. Hybrid Cloud This general-purpose term seems to provide a comfort zone for many enterprise IT managers. It sounds reassuring to be able to work with one of the major public-cloud providers like AWS or Microsoft Azure while still maintaining an on-site presence.
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Phil Hombledal, Solution Architect at CollabNet, discussed how customers are able to achieve a level of transparency that e...
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, showed how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningful f...
Logs are continuous digital records of events generated by all components of your software stack – and they’re everywhere – your networks, servers, applications, containers and cloud infrastructure just to name a few. The data logs provide are like an X-ray for your IT infrastructure. Without logs, this lack of visibility creates operational challenges for managing modern applications that drive today’s digital businesses.
Keeping pace with advancements in software delivery processes and tooling is taxing even for the most proficient organizations. Point tools, platforms, open source and the increasing adoption of private and public cloud services requires strong engineering rigor – all in the face of developer demands to use the tools of choice. As Agile has settled in as a mainstream practice, now DevOps has emerged as the next wave to improve software delivery speed and output. To make DevOps work, organization...