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

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