[v2] Cache Service

[EngHabu]

Motivation: Why do you think this is important?

Implement Cache Service interface/service

Goal: What should the final outcome look like, ideally?

Implement OSS flyteidl2 cache service

Describe alternatives you've considered

N/A

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

There is no explicit mention of a "Cache Service interface/service" or an "OSS flyteidl2 cache service" in the provided data sources. However, Flyte's caching is managed at the task level, with cache keys and behavior controlled via task decorators and configuration, and the backend cache logic is handled by components like datacatalog and FlytePropeller, not a standalone cache service interface as described in your request. The closest related concepts are the cache serialization API and cache eviction mechanisms, which are integrated into the existing Flyte backend services, not as a separate cache service interface or flyteidl2 service definition (source, source).

If you are proposing a new interface or service for cache management in Flyte v2 (OSS flyteidl2), this would be a new feature not currently present in the documented system. You may want to clarify the requirements and intended scope, as current caching is tightly integrated with task execution and datacatalog, rather than being exposed as a standalone service (source, source). Would you like more detail on how caching is currently implemented in Flyte and where a service interface might fit?

Sources:

• https://github.com/flyteorg/flyte/blob/master/rfc/core%20language/1461-cache-serialize-api.md
• https://github.com/flyteorg/flyte/blob/master/rfc/system/2633-eviction-of-cached-task-outputs.md

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!