-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Scaling an ADK Assistant to 100+ Programs #4217
Copy link
Copy link
Closed
Labels
answered[Status] This issue has been answered by the maintainer[Status] This issue has been answered by the maintainercore[Component] This issue is related to the core interface and implementation[Component] This issue is related to the core interface and implementationquestion[Component] This issue is asking a question or clarification[Component] This issue is asking a question or clarificationrequest clarification[Status] The maintainer need clarification or more information from the author[Status] The maintainer need clarification or more information from the authorstale[Status] Issues which have been marked inactive since there is no user response[Status] Issues which have been marked inactive since there is no user response
Metadata
Metadata
Assignees
Labels
answered[Status] This issue has been answered by the maintainer[Status] This issue has been answered by the maintainercore[Component] This issue is related to the core interface and implementation[Component] This issue is related to the core interface and implementationquestion[Component] This issue is asking a question or clarification[Component] This issue is asking a question or clarificationrequest clarification[Status] The maintainer need clarification or more information from the author[Status] The maintainer need clarification or more information from the authorstale[Status] Issues which have been marked inactive since there is no user response[Status] Issues which have been marked inactive since there is no user response
We currently have an ADK-based learning assistant implemented for a single program. The assistant works well, but the current setup assumes a one-to-one relationship between a program and the server/runtime (program-specific prompts and learning data are coupled to the deployment).
We are now looking to scale this learning assistant to support 100+ mastery programs, where:
The key challenge is designing a clean, maintainable way for a single ADK runtime to dynamically load:
program-specific configuration (prompts, persona, rules)
program-specific learning data (lessons, transcripts, precomputed artifacts)
…at runtime, based on a
program_id, without introducing brittle branching logic, duplicated code, or performance regressions.What We’re Considering
Our current thinking is to:
Before locking this in, we’d love to sanity-check this approach with the community.