The revolution in data synchronization — the Open Integration Hub enables simple data synchronization between any software applications and thus accelerates digitalisation
Visit the official Open Integration Hub homepage
The Open Integration Hub enables data synchronization across a variety of applications. To create a connection and enable interaction a link is needed between the software application and the Open Integration Hub - namely an Open Integration Hub connector. A connector connects a software solution to the Open Integration Hub. It consists of two distinct parts, namely adapter and transformer. It contains different functionalities e.g. to fetch and transform data. These functionalities are further explained in the sections adapter and transformer. In order to achieve our goal to establish a successful open source community we need to steadily increase the number of connectors. So join us and help us grow as an open source community!
The following illustration provides a holistic overview of a connector:
An adapter is a module for the syntactic connection of an external application and its data to the Open Integration Hub. This includes protocol translation, data format transformation, etc. Furthermore it provides functionalities to perform e.g. CRUD operations within the source system.
For further information please read through the information within the [adapter folder](/Adapters).
A transformer is responsible to semantically transform an incoming JSON object into another JSON object. Thus the mapping between two data models is done within the transformer.
For further information please read through the information within the transformer folder.
Before you contribute please read our contribution guidelines.
To see how members of the community are expected to behave, please read the code of conduct. We apply the code of conduct defined by the Contributor Covenant, which is used across many open source projects, such as NodeJS, Atom and Kubernetes.
When looking for further information or support, please contact: philipp.hoegner@cloudecosystem.org.
- Adapters: Describes the adapters, their goals, standardized behavior and checklists for building an adapter
- ApplicationDocuments: Contains all application documents needed to apply for the funding of the creation of a connector
- Protocols: Collection of all taken protocols by the workgroup
- Transformer: Includes the transformer concept, a basic introduction into the JSONata transformation language, transformer evolution and suggestions for possible implementations
- CONTRIBUTING: Contains the contribution guideline for the Open Integration Hub project
- CODE_OF_CONDUCT: Contains an explanation of the expected behavior of the community members, following the code of conduct defined by the Contributor Covenant
- Each workgroup has atleast one status call every two weeks
- Every committer must attend the status call
- The governance model defines the workgroup members' roles into managers, committers or contributors
| Member Name | GitHub Alias | Company | Role |
|---|---|---|---|
| Philipp Hoegner | philecs | Cloud Ecosystem | Manager |
| Robin Brinkmann | RobinBrinkmann | Cloud Ecosystem | Committer |
| Jacob Horbulyk | jhorbulyk | Elastic.io | Committer |
| Renat Zubairov | zubairov | Elastic.io | Contributor |
| Dennis Steiniger | dennisCES | Cloud Ecosystem | Contributor |
Within the project different terms and abbreviations are frequently used. All terms and abbrevations are explained within the glossary and our list of abbrevations.