Skip to end of metadata
Go to start of metadata
Mission Statement
To allow standard software to coexist nicely with SOA and to reach SOA Maturity Level 2, we need to master our Business Objects.‏ EDR is the natural, lean, simple and inexpensive choice for a Master Data Management Services.
  • Simplest possible route to managed data
  • Reduced complexity by zooming in to one single Business Object at a time
  • All non-business object relations handled as resource references.
  • Simple first generation implementation within 2-3 months
  • By adding support for managed Business Objects in your SOA, you facilitate and enable event-driven architectures and real- time enterprise.

Intro

Service Oriented Architecture is all over us. There seems to be some kind of consensus that one type of SOA services are services that are responsible for the core business objects - and vendors are monitoring and releasing their SOA Data Server products to close the gap. By pioneering the SOA space with EDR, we have gained lots of valuable of experiences of how to solve the Master Data challenges in SOA.

The problem

  • Companies don't have a precise view about their data
  • Projects define data reconciliation outside project scope
  • Developers do not care about data
  • Vendors always try to solve to much at once
  • The data warehouse guys have beards and funny accents

NB. The problems description needs major rework - most people does not get the message. possibly by using some example cases..

The vision

To solve the data problems in the simplest and most flexible way and at the same time provide a solid building block on the way to enable the Real Time Enterprise vision for a service-oriented System Strategy. EDR-MDS is primed to be the best strategy to move to SOA Maturity Level 2. (SOA Maturity Models and EDR-MDS)

EDR-MDS

To allow standard software to coexist nicely with SOA, we need to master our disjoint Business Objects (EDR sources)‏ EDR is the natural, simple and inexpensive choice for a Master Strategy for Business Objects.

Highlights

  • Field/value based mastering (dynamic readable rules(DSL))‏
  • Auto-update/write-back to all involved parties (using the standard provider)‏
  • Out-of bounds mastering/overwrite to leverage the most of all applications
  • Out-of-bounds triggers for each provider

Backbones

  • JavaSpace (Blitz)
  • EDA/Eventing
  • Federated backbones
  • Distributed cache

Tooling

  • JMatter Domain Object Management Client

Mastering with EDR

Initial discussions identified some core concepts related to mastering strategies. These concepts requires definitions in this context:

  • Master
  • Synchronization
  • Mapping
  • Complex Validation

All mastering strategies are primarily focused towards categorized Core Services implementing Enterprise Domain Repository and utilizing multiple providers.

Key takeaways

  • Simplest possible route to managed data
  • Reduced complexity by zooming in to one single Business Object at a time
  • All non-business object relations handled as resource references.
  • Simple first generation implementation within 2-3 months
  • By adding support for managed Business Objects in your SOA, you facilitate and enable event-driven architectures and real- time enterprise.
  • Value Delivered - Business Cases
There is no such thing as magic
EDR-MDS is just good old common sense
  • EDR-MDS can be implemented in your favorite technology, container, product or programming language.

Quick links


UserEditsCommentsLabels
Thor Henning Hetland 3121

Labels:
glossary glossary Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.