Data Integration: Solution Integration: An Approach to Ensure Failure | DM Review | Industry Led, Industry Read
Unfortunately, organizations still remain that attack this issue with no functional or strategic planning in place.
How can the provider define the strategy?
Why would we want the provider to define the strategy? Tactics, maybe, but not strategy.
Reading on – I am taken by the definition of POC – proof of concept – as opposed to piece of crap.
We have had a 10+ year proof of concept in the integration part. Isn’t it about time to find a real strategy?
Thoughts from the Integration Consortium: Dynamic Interoperability and Service-Oriented Architectures, Part 2 | DM Review | Industry Led, Industry Read
Services have technology-independent interfaces. Services are exposed using standards-based, identical interfaces which makes them easy to use, reuse and guarantees dynamic interoperability.
- Services are loosely coupled. Services can be created without any forethought for how or who will consume them. In addition, any changes are made to the implementation of the service will have no ripple effect to consumers of the service.
- Services are coarse grained. Services focus on high-level business process using standard interfaces and so mask the underlying technical complexity and operational intricacies of how the service is implemented.
- Services are modular. A service represents a discrete unit of business, application or system functionality. Multiple services can be combined to deliver more valuable services. This modular approach gives organizations great flexibility in system design. By reassembling services into a new configuration, a business can create a new business service to support a different business objective.
Replace the word “Services” above with the concept of a data source. Doesn’t that make some sense?
Thoughts from the Integration Consortium: Web Services-Based Integration, Part I | DM Review | Industry Led, Industry Read
Second, Web services can be used to expose business and application logic in a standardized way that makes it easy for any other Web services to consume.
I’m posting this for reference.
What about treating each of the data sources as a “Web Service”? The abstraction process seems to be similar to what we need to do when moving data into information.