For an integrated platform with proper metadata management, it should only have 1 connection to a unique sources for a connection type to ensure re-usability.
However, it need to allow using of difference UserID and Password from security perspective.
For example, there's at least 3 ways to connect to Db2 -
- Db2 Connector using Db2 Client
- Db2 JDBC using Db2 JDBC Driver
- Db2 ODBC using Db2 ODBC Driver
- etc.
For each unique sources, it should only have 1 unique connection of 1 connection type.
At the same time, we need to be able to search and filter all those connection as we will start to have thousands of connections in 1 place.
For example, search by hostname, database name, filter by connection type like JDBC, ODBC, etc.
Not sure whether this will ensure a unqiue connection name - Source Type (Db2, Oracle, etc) + Connection Type (JDBC, ODBC, Client, REST API, etc) + Hostname + DB.
------------------------------
HOW MING YONG
------------------------------
Original Message:
Sent: Thu October 14, 2021 01:20 PM
From: Brett Witteck
Subject: 🎟 5. Platform-wide view of data source connections?
Connections are assets that allow you to access & work with your external data. Connecting to your data can happen in different contexts and locations on the platform. How do you keep track of all your connections?
🎟 For 1 raffle entry, tell us how helpful would it be for you to have a single view of all the connections you have access to on the platform (or an administrative view of all connections created on the platform), and how would you expect to utilize such a view in the context of your work?
🎟 Bonus ticket time 🎟 If you could have a platform-wide view of only one asset type (e.g. notebooks, models, dashboards, connections, data etc.) which would you choose and why?
#InnovationJam #InnovationJamOct2021
------------------------------
Brett Witteck
------------------------------
#CloudPakforDataGroup