Through Dipforge's Architecture integration has been made easy. This has been achieved through a simple design principal, all writes are driven through a workflow or ESB(Enterprise Service Bus) engine and all reads are perform on secondary read only stores. This means that in Dipforge we have the best of both worlds at our disposal, the speed of reading against local storage, and the flexibilty of making changes via an ESB. As a result development is rapid and integration is easy.
This means that updating the graph store or integrating with a service end point is equally simple, each involve invoking an end point in a workflow script. All workflow scripts are driven by actions being performed on graph defined entities and the integration follows these steps:
- Define a entity type and publish
- Write a groovy end point script to manage the integration with the external system
- Define the mapping of the groovy end point script and publish
- Write a workflow script to invoke the end point and persist the entity
- Define the action on the type that will invoke the workflow and publish.
Once these simple steps have been completed any time the action is invoked the workflow will be executed and changes to both the graph store and external system will be made.