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

Organizations that fail to coordinate EDM and SOA strategies appropriately will inherently cause enterprise data and services to evolve disparately rather than synergistically as part of a well-managed enterprise architecture, and should ask:

  • How will the master data and metadata used in services/transactions be managed?
  • How will SOA services be developed/maintained to use only standardized master data, metadata, and "gold standard" data?
  • How will processes and data integration, as well as overlapping roles/responsibilities and ownership/stewardship concerns for data utilized or made available by services, be managed between parallel data and SOA governance programs?

These are important issues from the EDM perspective that may go unmanaged when organizational data and service strategies, governance, architecture, and development go uncoordinated.

The Enterprise Information Architecture (EIA) component, a primary coordination point, is relatively recent to EDM organizations. It:

  • Comprises information, business processes, and architectures
  • Includes information knowledge worker "bridge" staff who understand the business, and communicates with technical staff
  • Determines type, content, and quality of enterprise information delivered by SOA (via data/SOA governance)
  • Creates policies/standards for enterprise information usage

Figure 4 shows how EIA works with organizational business processes and the SOA, under the guidance of data/SOA governance. It is directly leveraged by the SOA and includes the enterprise data model that service designs will leverage. Hence, the EIA works with and contains the enterprise-level aspects of MDM and metadata management. It coordinates pertinent data integration and quality issues, best practices, and tools between EDM and SOA strategies as a primary EDM component for coordination with SOA strategies.

SOA Framework and Component Considerations
Looking similarly at a SOA framework, it becomes clearer where dependencies and synergies between EDM and SOA strategies exist.

SOA initiatives generally address several of the components shown in Figure 5, simultaneously or at least in coordination. Considering how EDM components are impacted in a SOA environment, most SOA components play some role in coordinated EDM-SOA strategies/programs.

Key cross-impacts of EDM and SOA components in a SOA environment are:

  • SOA Governance: Data governance ensures that services use the right data/metadata, and any proliferation of data for or by services is managed for quality/consistency. For service-related data/metadata, coordinated data-SOA governance is needed.
  • Workflow Management and Business Rules: Metadata management includes common automation and workflow routing rules, business rules, and SLAs.
  • Access and Security Services: MDM includes security classifications for master data and user entities, while metadata management includes descriptions and rules for handling service/data classifications.
  • Enterprise Business Services: MDM ensures the availability and evolution of master data supporting fine-grained data and composite business services. Metadata management ensures services use appropriate workflows, business rules, SLAs, etc. Meanwhile, EIA (e.g., data architecture) is referenced by service releases.
  • ESB: Metadata management drives configuration rules of the ESB for transaction/message processing.
  • Enterprise Data Platform Services: MDM and EIA are referenced.

SOA Best Practice Considerations
Another way to consider SOA strategy impacts on and synergies with EDM is in addressing how organizations achieve SOA best practices. Significant dependencies between an organization's EDM and SOA strategies will surely reveal themselves and must be taken into account when pursuing SOA best practices.

The following are among the key best practices for SOA strategies, and most/all can also be applied as EDM best practices.

1. When thinking about services, don't forget to consider the data
Systematically designing a service model is like designing a data model. For either, its impact should be considered long term, and the level of normalization of designed components, services, or data is considered a sign of quality and maturity.

Figure 6 shows service-data normalization from immature to mature organizations:

  • "Wild West": Non-existent or ad hoc and uncoordinated normalization
  • Ownership/Stewardship: Service designs built on data designs
  • Encapsulation: Service and data designs coordinated in development/maintenance initiatives; either may drive the other as long as they are coordinated
  • Object: One and the same service/data designs. Normalized designs are within EIA designs; service implementations take data ownership to another level where master data value is known only in service designs/implementations.

Most organizations pursuing services-data normalization have progressed to ownership/stewardship levels, yet need to reach encapsulation before realizing major benefits in efficiencies, maintenance costs, and asset business value.

The highest level of service-data normalization, object, may not make sense for some organizations, especially where master data or business services change frequently. Depending on their stability, the more possible an object level may be. However, cost/benefit analysis may make encapsulation preferred for some organizations.

Transitioning to advanced service-data normalization is a process of increasing organizational maturity toward coordinated EDM-SOA strategies.

This is facilitated through coordinated:

  • Data and SOA governance organizations and programs
  • MDM, metadata management, and EIA with SOA initiatives' enterprise services architecture/development

2. Focus on avoiding the proliferation of services that can't be shared
SOA strategies have little business value if their enterprise services aren't shared (i.e., reused) among multiple user groups and business domains in the enterprise and sometimes outside the immediate enterprise.

Not coordinating data with SOA initiatives (e.g., via governance), services may inadvertently propagate non-"gold standard" data to service consumers when developed by the initiatives. Such services become, or should be, unable to be shared.

Worse, the absence of coordinated data and services may tempt developers to create their own data stores/marts to support their services' domain, causing unnecessary propagation of potentially unmanaged databases. This will damage both your EDM and SOA strategies.

Avoiding services that can't be shared is facilitated by coordinated:

  • Data and SOA governance organizations and processes
  • EIA and enterprise data model, with SOA services portfolio and releases
  • MDM and metadata management with SOA services' initiatives architecture/design

3. Reward both reusability and reuse
Reusability and reuse applies to services and data in development, deployment, and consumption cycles. Services and data should be normalized for reuse (see SOA Best Practice #2), and developers and consumers of either should be rewarded.

This is a delicate balance that should be managed by data-SOA governance and processes to ensure appropriate reuse when it makes business sense (i.e., unless service/data requirements are new or existing designs/implementations are obsolete).

SOA governance will sometimes advocate development of new or improved services when it makes sense. Similarly, data governance will almost always advocate reuse of existing master data or managed metadata, but decreasingly over time as managed data stabilizes, there may be reasons to extend or change "gold standard" data.

Reuse and reusability should also be enforced, and best practices established, by coordinated data and SOA governance programs. Governance should include the identification of which data and services can potentially be reused for a given initiative, and the criteria for when new data/services should be created or modified.

Rewarding reusability/reuse is facilitated by coordinated:

  • Data and SOA governance organizations and processes
  • EIA, MDM, and metadata management processes/tools with SOA services' initiatives architecture and design processes/tools

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...