docs: add multi-agent reference architecture - #1030
Open
malladinagarjuna2 wants to merge 2 commits into
Open
Conversation
This provides a reference architecture for deploying multiple agents within a single Quarkus application. Fixes a2aproject#898
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR adds a reference architecture documentation page detailing how to scale A2A Server Agents by hosting multiple distinct agents within a single Quarkus application.
Fixes #898
The Problem
Deploying a single agent per Quarkus app (1:1 mapping to kubernetes pods) incurs significant operational overhead and resource consumption when the number of agents grows into the hundreds. Users needed official guidance and a reference architecture for deploying multiple
AgentCards and JSON-RPC handlers from a single application platform.The Solution
Added a dedicated
Multi-Agent Scalingpage to the documentation site. The guide explains how to bypass the default@ApplicationScopedsingletons and manually register Vert.x routing paths for individual agents (e.g.,/{agentId}/.well-known/agent-card.json), allowing a single app to dynamically host an unlimited number of agents with minimal overhead.