Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Yeshim Deniz, Elizabeth White, Stackify Blog

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) View Comments

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.


Most Recent Comments
graham_charters 11/10/08 05:51:15 AM EST

Thanks for posting this information.
I agree that EDM and MDM are growth areas at the moment, with more and more companies recognising the benefits - both business and economic - that these types of technologies provide.
And companies such as Initiate Systems (www.initiatesystems.com) are ideally placed to deliver these solutions.

@MicroservicesExpo Stories
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
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, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
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...
"DivvyCloud as a company set out to help customers automate solutions to the most common cloud problems," noted Jeremy Snyder, VP of Business Development at DivvyCloud, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
In his session at Cloud Expo, Alan Winters, U.S. Head of Business Development at MobiDev, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to maximize project result...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...