Replies: 1 comment 2 replies
-
|
Since the lifecycle of entities stored in a Catalog and a Registry typically differs, and considering the need for high availability, I believe that a REST Data Catalog like Unity Catalog (OSS) is not well-suited for this use case. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I agree—the lifecycle and operational requirements of AgentCards differ significantly from traditional cataloged entities, making a REST-based Data Catalog like Unity Catalog (even OSS versions) less suitable for this use case. AgentCards often represent active, dynamic agents with capabilities and context that may change in real time, requiring low-latency updates, fast discovery, and immediate consistency—whereas catalogs are optimized for relatively static metadata, versioning, and governance over longer-lived assets like datasets or models. Additionally, registries intended for agent coordination often need built-in support for real-time subscription, health checks, and distributed availability, which Unity Catalog lacks. So while it can be used for persistence or archival, it falls short as a primary registry for active agent orchestration. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe agents will have bookmarks of URLs like '/.well-known/agent.json', just like we have our favorite bakery, supermarket, or clothing store. lol |
Beta Was this translation helpful? Give feedback.
-
Unity Catalog is an open source data catalog that has been widely adopted within the Enterpirse Data Engineering Community.
It interfaces well with Iceberg Catalogs, MLFlow, and supports registering "AI" Functions.
www.github.com/unitycatalog/unitycatalog
Beta Was this translation helpful? Give feedback.
All reactions