Overview
Why Canonical Model Management Is Needed
Why Canonical Model Management Is Needed
The vast majority of large enterprises are moving away from point to point integration in an effort to speed up integration projects and reduce costs. This in turn supports the enterprise goals of being more agile and competitive. In some cases the sheer number and complexity of back end systems means point to point integration is no longer viable.
Any Enterprise Integration initiative will need a canonical model approach to harmonize their data in motion, if they are to be successful. Most start out with simple XML Schemas and schema editing and source code repositories. This approach inevitably hits scalability issues. It is hard to collaboratively evolve and version the Canonical Model, there is a lot of resistance to adoption of the model as these tools require a lot of manual extra work to create a consumable schema from the model, and there is no governance of the semantics used and therefore no effective reuse.
The majority of our customers have reached this stage and for these reasons chose to roll-out igniteXML to support their Canonical Management efforts.
A canonical Model Management system like ignite XML ensures that all messages, services and XML schema are:
- 100% consistent and built from the approved version of the Canonical Model
- Optimized for run-time
- Clearly Understood
- Easy to maintain
- Mapped to data models
This delivers:
- Maximum reuse and agility
- Optimized run-time performance
- Less work and faster delivery
- Lower integration costs
- Data Governance
