Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Elizabeth White, Stackify Blog, Andreas Grabner

Related Topics: Microservices Expo

Microservices Expo: Article

The Case for Coordinated EDM and SOA Strategies

And what strategic EDM & SOA components require attention to facilitate the appropriate coordination - Part 1

4. When establishing governance, stay away from dictatorships
As shown in Figure 7, there are three general governance approaches for organizations:

  • "Wild West": Non-existent or ad hoc and uncoordinated governance. Lack of enterprise-level coordination, with minimal governance processes/roles developed out of necessity in selected domains.
  • Federated: Coordinated independent efforts between domains. Selective enterprise coordination, but standards, best practices, and tools are inconsistent between domains. Also inconsistent coordination points with business requirements, etc., between domains.
  • Dictatorship: Centralized control of all data or service assets; all assets considered from an enterprise perspective, which is not as effective for domain-specific assets. Here, everything is coordinated at the cost of domain flexibility.

The goal is not to progress to dictatorial governance. While "Wild West" is a problem with lack of control/coordination, dictatorships swing the pendulum too far toward centralized control of all decisions regarding enterprise-wide and domain-specific assets (data or services).

Establishing balanced governance is facilitated by coordinated:

  • Data and SOA governance roles and processes
  • Enterprise-level EDM assets (EIA, MDM, metadata management) with enterprise-level SOA assets (enterprise architecture, SOA services model, and services portfolio)
  • Enterprise-level EDM and SOA architecture and design processes/tools

5. Establish a Center of Excellence (COE) to provide guidance, governance, and coordination
A well-organized and managed EDM or SOA environment should establish a COE to:

  • Involve appropriate stakeholders (business/IT) early and often
  • Facilitate necessary coordination between interdependent projects, programs, and organizational divisions

Mature EDM/SOA strategies include development and management of a supporting COE. However, there is the danger of organizations developing disparate EDM/SOA COEs when pursuing both strategies, despite overlapping roles, dependencies, and synergies.

As Figure 8 demonstrates, an Integration Competency Center (ICC) does more than a traditional COE by providing a design, development, prototyping, and testing sandbox for data and services integration.

An ICC provides processes/tools for EDM and SOA environments, and facilitates coordinated services and information architecture and development to achieve, among other things, service-data normalization.

An ICC coordinates with data-SOA governance and the EIA, as well as overall enterprise architecture concerns. It identifies key components managed within governance for which instances will reside in the ICC and/or production implementations.

Establishing a services-data COE/ICC for stakeholders and interdependent projects is facilitated by coordinated:

  • Data and SOA governance roles and processes
  • EIA and its enterprise data model, with SOA services portfolio and releases
  • EIA, MDM, and metadata management processes/tools with SOA services' initiatives architecture and design processes/tools
  • Enterprise-level EDM assets (EIA, MDM, and metadata management) with enterprise-level SOA assets (enterprise architecture, services model, services portfolio)
  • Enterprise-level EDM and SOA architecture and design processes/tools

6. Start with the right program size in the right area of emphasis
Starting too big with EDM or SOA can lead to mistakes. Think strategically, but act tactically with an emphasis on launching a realistic program that can become successful initially and grow. Develop a coordinated long-term vision for your EDM/SOA programs, and implement these incrementally in support of each other. Coordinated data-SOA governance programs, and a supporting COE/ICC that addresses data and services (see Best Practice # 5), can support the scoping and launch of a "right-sized" program.

For example, you can design sets of services around selected business and data models. The data model can be used to encapsulate business data, and the business model can link further business processes of applications with its software implementation (i.e., services). Business services typically consume data services that are usually not exposed outside the enterprise.

Alternatively, the data model may become primary design criteria for an application; the data model would be the best choice on which to base application services, user interfaces, and business process designs.

Implementing an appropriately sized and focused EDM-SOA program is facilitated by coordinated:

  • Data and SOA governance organizations and processes
  • EDM/SOA COEs (or ICCs) with the EIA and enterprise data model, and the SOA services portfolio and release management

7. Invest in systematically designed core services initially, allowing for rapid opportunistic extensions later
An SOA program may be launched tactically with flexibility and scalability to systematically incorporate program scope under the guidance of governance and an ICC.

Key intermediary services that intercept and handle operations common across services that should be reused include: authentication, logging, monitoring, and routing.

A common data services layer:

  • Provides abstraction between producers and consumers of data; service and data consumers are insulated from complexity, location, and changes in source systems
  • Presents services/data consumers, whether human, application, or services, with aggregated views from multiple sources
  • Manages, monitors, and reports on the enterprise views of data/metadata

SOA strategies cause organizations to implement an EIA and infrastructure in support of services, including common data services capable of supporting producers and consumers with timely and consistent information.

The main categories of data services include:

  • Enterprise Data Services: Directly around the data (e.g., retrieve, update). Also enablement of traditional MDM functionality (e.g., data quality/harmonization across systems exposed as services).
  • Enterprise Metadata Services: Around metadata (e.g., retrieve master data schema). SOA designers/developers creating business services, and those consuming them, reference organizational master data schemas via services.
  • Enterprise Data Platform Services: Around services/data platforms, including management, monitoring, and reporting.

Within other services, and across the data services layer, common infrastructure methods for search, access, creation, update, and deletion functionality are made available.

Systematically/progressively designing services is facilitated by coordinated:

  • Data and SOA governance organizations and processes
  • EIA and its enterprise data model, with SOA services portfolio and releases
  • EIA, MDM, and metadata management processes/tools with SOA services' initiatives architecture and design processes/tools
  • EDM/SOA COEs (or ICCs) with the EIA and enterprise data model, and SOA data with infrastructure services releases

Conclusion
This article demonstrates the case for coordinated EDM and SOA strategies and capabilities in organizations. It further shows what strategic EDM and SOA components require attention to facilitate appropriate coordination.

This article shows that organizations should develop a coordinated data-SOA governance program, as coordination needs to be established at leadership levels to enable the optimal value of their services and data. This is the highest priority toward coordinated EDM-SOA capabilities.

Initial data/SOA governance models should be coordinated for processes, checkpoints, and ownership. We rarely develop these strategies and governance models in coordination from scratch though hopefully this article will spark this. Hence, it's important to adapt appropriate processes and checkpoints between separate models and (re)define roles to support coordinated data-SOA governance.

Organizations should scale progressive EDM-SOA initiatives with shared data-SOA governance, processes, and communications complemented by educating EDM/SOA resources/stakeholder to effectively leverage each other in joint data-services development.

Ensure business- and data-modeling analysts are involved in services design (e.g., not just services analysts), so business functionalities are reflected rather than technical partitioning of software/data. An appropriate COE/ICC will facilitate diverse stakeholders working proactively to drive phases of coordinated EDM-SOA initiatives. Last, promote a culture of collaboration as an underpinning of successful EDM, SOA, and coordinated programs.

Part 2 of this series on EDM and SOA will introduce the coordinated service-oriented data architecture framework and the capability maturity model (CMM), including how to use the C-SODA framework and CMM to drive assessments and improvement roadmaps for organizational maturity.

More Stories By Keith R. Worfolk

Keith R. Worfolk is a senior architect with Hitachi Consulting. He has more than 21 years of senior IT management and executive-level success in strategic enterprise architecture, software development, and large-scale systems integration. He has strong international and Big 5 project experience. Keith earned an MBA from Duke University.

Comments (1)

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.


Microservices Articles
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, will discuss how to use Kubernetes to setup a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace....
SYS-CON Events announced today the Kubernetes and Google Container Engine Workshop, being held November 3, 2016, in conjunction with @DevOpsSummit at 19th Cloud Expo at the Santa Clara Convention Center in Santa Clara, CA. This workshop led by Sebastian Scheele introduces participants to Kubernetes and Google Container Engine (GKE). Through a combination of instructor-led presentations, demonstrations, and hands-on labs, students learn the key concepts and practices for deploying and maintainin...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and micro services. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your contain...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
DevOps is speeding towards the IT world like a freight train and the hype around it is deafening. There is no reason to be afraid of this change as it is the natural reaction to the agile movement that revolutionized development just a few years ago. By definition, DevOps is the natural alignment of IT performance to business profitability. The relevance of this has yet to be quantified but it has been suggested that the route to the CEO’s chair will come from the IT leaders that successfully ma...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, will discuss why containers should be paired with new architectural practices such as microservices ra...