You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 13, 2025. It is now read-only.
I have a few questions regarding various use cases:
Support for large data
Are there plans to add streaming support in the runtime? On the client, It looks as if the connector materializes the entire entity into memory as opposed to streaming segments during processing. My understanding is the core IDS Information Model classes assume this. Or have I misunderstood this? For example, the contents of an IDS artifact response could be a pointer to a data stream that is processed at some later point downstream? Streaming support could be really challenging, particularly in the context of policy handling, but it's a common requirement in environments that process large amounts of data.
Integration with other data transfer technologies
Companies may already be using existing technologies that they would like to leverage in the context of data transfer. For example, a company may be using cloud object storage for machine learning data sets. Object storage systems often have APIs that are optimized for highly parallel data transfer. Is it possible for the connecter to leverage these technologies? For example, the connector implements the trust flow and initial data request; however, the actual data transfer is completed by out-of-process infrastructure that uses those storage technologies. Note that this would be different than the connector using a "data app" that it provisions as a Linux container. These other technologies would be infrastructure that is deployed outside the ambit of the connector (possibly for security reasons).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a few questions regarding various use cases:
Are there plans to add streaming support in the runtime? On the client, It looks as if the connector materializes the entire entity into memory as opposed to streaming segments during processing. My understanding is the core IDS Information Model classes assume this. Or have I misunderstood this? For example, the contents of an IDS artifact response could be a pointer to a data stream that is processed at some later point downstream? Streaming support could be really challenging, particularly in the context of policy handling, but it's a common requirement in environments that process large amounts of data.
Companies may already be using existing technologies that they would like to leverage in the context of data transfer. For example, a company may be using cloud object storage for machine learning data sets. Object storage systems often have APIs that are optimized for highly parallel data transfer. Is it possible for the connecter to leverage these technologies? For example, the connector implements the trust flow and initial data request; however, the actual data transfer is completed by out-of-process infrastructure that uses those storage technologies. Note that this would be different than the connector using a "data app" that it provisions as a Linux container. These other technologies would be infrastructure that is deployed outside the ambit of the connector (possibly for security reasons).
Thanks for your help!
Jim
Beta Was this translation helpful? Give feedback.
All reactions