Welcome!

Microservices Expo Authors: John Rauser, Liz McMillan, Madhavan Krishnan, VP, Cloud Solutions, Virtusa, Jason Bloomberg, Pat Romanski

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
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
"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...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
"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.
"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.
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, 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.
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, 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 nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
Digital transformation has changed the way users interact with the world, and the traditional healthcare experience no longer meets rising consumer expectations. Enterprise Health Clouds (EHCs) are designed to easily and securely deliver the smart and engaging digital health experience that patients expect today, while ensuring the compliance and data integration that care providers require. Jikku Venkat