Model Hub img-beta-icon@2x

Models Are Everywhere

Database schemas, message formats, UML diagrams and spreadsheets are structured information models that describe your business data. Our challenge is to comprehend these models, assimilate them, and put them to work. Even when they aren't expressed in our preferred modeling language.

The Problem: Model Mismatch

API Management, service-oriented API design, and master data management programs are often hampered by the complexity of divergent model formats. We want to manage APIs and data types in a canonical form, but we need to recognize existing models that are already expressed in other forms: UML, XML Schema, WSDL, ERD, and various domain-specific languages.

Moreover, these models may be living documents, with ongoing evolution in their original forms, so a one-time import into a new API catalog isn’t a realistic option.

With a heterogeneous, constantly changing landscape of models, how can we hope to maintain a master catalog of service APIs and data type definitions that reflects the current state of these models?

Keep the Wheel, Reinvent the Hub

Model Hub™ provides the architecture for large-scale model interchange, using a flexible set of mapping structures and algorithms that work across different modeling languages. As the industry’s first true model synchronization engine, Model Hub is designed to allow full control and customization over the synchronization process.

Model Hub is an ideal solution for model standardization, assimilating disparate models into a designated organizational standard format.

Model Hub also supports best-of-breed strategies for model editing, allowing the use of commercial or open source tools to edit and visualize models, while synchronizing these standard models with proprietary or legacy model formats.


Feature Highlights

  • Preserves models in their original form, and allows ongoing model evolution.
  • Persistent mappings and intelligent diff algorithms isolate recent changes from pre-existing model elements, allowing efficient refresh.
  • Allows for variations in the form of the model on one or both sides. For a given construct in one model, there may be multiple, semantically equivalent ways of representing that in the other model.
  • Provides a customizable rule set for propagating changes in one model to corresponding changes in the other.
  • Manages conflicts, where a given model element has changed on both sides.
  • Gives clear feedback to the user before committing changes to a model, providing transparency into the model synchronization process.
  • Affords full control over the propagation of changes, so the user can choose how to handle a change in one model, and decide whether and how to translate that change into the other model.
Model Hub is in limited beta. Contact us to join the beta program or learn more about Model Hub.