Integration Hub
From the book I Am Datapedia!, published here free by the author.
Integration Hub is normally confused with datastores like Data Warehouse, Data Lake, Data Lakehouse etc., which is not correction.
Integration Hub is a single central place from where you can send instructions to internal and external systems to perform some actions. Integration Hub consists of Spokes, each Spoke consists of number of steps for actions.
Generics Steps
- Create actions to be sent out to external systems.
- Run commands on external servers.
- Allow sending messages e.g., Rest, SOAP etc.
- Allow parsers.
- Allow SQL command to databases.
Yes, we do it every day e.g., we create connections with any system e.g., creating a connection with SharePoint then running commands to Delete a file. Consider 100 users want to do the same action, each must go through the same number of steps. Using Integration Hub, Spokes consisting of connections, credentials, and actions to be performed on e.g., SharePoint. Now, all those 100 users can reuse the same Spoke created to delete files in SharePoint.
Now a days, most of the applications, portals, systems allow to use Spoke as it assists them to limit the actions in its system.
Generic Spokes: CISCO WebEx, MS Teams, Slack, Zoom, GitHub, Jira, Twitter, Dropbox, Google, SharePoint, Amazon/ AWS.
Why Integration Hubs?
- Third-party systems no longer allow custom connectivity.
- Pre-built spokes are the way forward.
- Pre-built spokes assist like no duplication connections for same set of data, no unknown data extracts, allowing data based on defined scope.
- Re-usability of Spokes
- Single interface
Express your reaction
Your Take on This Insight?
Share how this content resonates with you.
0 reactionsSign in to react or comment
Comments (0)
No comments yet.
Free account
You can read every topic without one. A free account lets you react to this topic, comment under it and search the Knowledge Hub. Reacting and commenting need a confirmed e-mail address.