Welcome!

Microservices Expo Authors: Pat Romanski, Stackify Blog, Elizabeth White, Steve Wilson, Mehdi Daoudi

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
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up 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. H...
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...
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
As many know, the first generation of Cloud Management Platform (CMP) solutions were designed for managing virtual infrastructure (IaaS) and traditional applications. But that’s no longer enough to satisfy evolving and complex business requirements. In his session at 21st Cloud Expo, Scott Davis, Embotics CTO, will explore how next-generation CMPs ensure organizations can manage cloud-native and microservice-based application architectures, while also facilitating agile DevOps methodology. He wi...
These days, change is the only constant. In order to adapt and thrive in an ever-advancing and sometimes chaotic workforce, companies must leverage intelligent tools to streamline operations. While we're only at the dawn of machine intelligence, using a workflow manager will benefit your company in both the short and long term. Think: reduced errors, improved efficiency and more empowered employees-and that's just the start. Here are five other reasons workflow automation is leading a revolution...
Cloud adoption is often driven by a desire to increase efficiency, boost agility and save money. All too often, however, the reality involves unpredictable cost spikes and lack of oversight due to resource limitations. In his session at 20th Cloud Expo, Joe Kinsella, CTO and Founder of CloudHealth Technologies, tackled the question: “How do you build a fully optimized cloud?” He will examine: Why TCO is critical to achieving cloud success – and why attendees should be thinking holistically ab...
In our first installment of this blog series, we went over the different types of applications migrated to the cloud and the benefits IT organizations hope to achieve by moving applications to the cloud. Unfortunately, IT can’t just press a button or even whip up a few lines of code to move applications to the cloud. Like any strategic move by IT, a cloud migration requires advanced planning.
Docker is on a roll. In the last few years, this container management service has become immensely popular in development, especially given the great fit with agile-based projects and continuous delivery. In this article, I want to take a brief look at how you can use Docker to accelerate and streamline the software development lifecycle (SDLC) process.
We have Continuous Integration and we have Continuous Deployment, but what’s continuous across all of what we do is people. Even when tasks are automated, someone wrote the automation. So, Jayne Groll evangelizes about Continuous Everyone. Jayne is the CEO of the DevOps Institute and the author of Agile Service Management Guide. She talked about Continuous Everyone at the 2016 All Day DevOps conference. She describes it as "about people, culture, and collaboration mapped into your value streams....
“Why didn’t testing catch this” must become “How did this make it to testing?” Traditional quality teams are the crutch and excuse keeping organizations from making the necessary investment in people, process, and technology to accelerate test automation. Just like societies that did not build waterways because the labor to keep carrying the water was so cheap, we have created disincentives to automate. In her session at @DevOpsSummit at 20th Cloud Expo, Anne Hungate, President of Daring System...
Did you know that you can develop for mainframes in Java? Or that the testing and deployment can be automated across mobile to mainframe? In his session and demo at @DevOpsSummit at 21st Cloud Expo, Dana Boudreau, a Senior Director at CA Technologies, will discuss how increasingly teams are developing with agile methodologies, using modern development environments, and automating testing and deployments, mobile to mainframe.
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
@DevOpsSummit at Cloud Expo taking place Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center, Santa Clara, CA, is co-located with the 21st International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is ...
While some vendors scramble to create and sell you a fancy solution for monitoring your spanking new Amazon Lambdas, hear how you can do it on the cheap using just built-in Java APIs yourself. By exploiting a little-known fact that Lambdas aren’t exactly single-threaded, you can effectively identify hot spots in your serverless code. In his session at @DevOpsSummit at 21st Cloud Expo, Dave Martin, Product owner at CA Technologies, will give a live demonstration and code walkthrough, showing how ...
If you are part of the cloud development community, you certainly know about “serverless computing”, almost a misnomer. Because it implies there are no servers which is untrue. However the servers are hidden from the developers. This model eliminates operational complexity and increases developer productivity. We came from monolithic computing to client-server to services to microservices to serverless model. In other words, our systems have slowly “dissolved” from monolithic to function-by-func...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
We define Hybrid IT as a management approach in which organizations create a workload-centric and value-driven integrated technology stack that may include legacy infrastructure, web-scale architectures, private cloud implementations along with public cloud platforms ranging from Infrastructure-as-a-Service to Software-as-a-Service.
IT organizations are moving to the cloud in hopes to approve efficiency, increase agility and save money. Migrating workloads might seem like a simple task, but what many businesses don’t realize is that application migration criteria differs across organizations, making it difficult for architects to arrive at an accurate TCO number. In his session at 21st Cloud Expo, Joe Kinsella, CTO of CloudHealth Technologies, will offer a systematic approach to understanding the TCO of a cloud application...
With Cloud Foundry you can easily deploy and use apps utilizing websocket technology, but not everybody realizes that scaling them out is not that trivial. In his session at 21st Cloud Expo, Roman Swoszowski, CTO and VP, Cloud Foundry Services, at Grape Up, will show you an example of how to deal with this issue. He will demonstrate a cloud-native Spring Boot app running in Cloud Foundry and communicating with clients over websocket protocol that can be easily scaled horizontally and coordinate...