a2aproject / a2aproject/a2a-java
How to scale a A2A production deployment to 100 A2A Server Agents each exposing a different AgentCard?
- Dominant language
- Java
- Stars
- 490
- Forks
- 172
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 55
Description
Say i have an quarkus App that implemented A2A SDK with on AgentExecutor and one AgentCard and i would like to scale this deployment to support a higher number of Server Agents.
the one approach that would work would be to deploy one separate Quarkus app per Agent to kubernetes and proxy the connection with a reverse proxy software creating virtual hosts/ingresses to access the Server Agent endpoint (AgentCard and JSONRPC handler)
```
https://a2a-server-agent-1/.well-known/agent-card.json
https://a2a-server-agent-2/.well-known/agent-card.json
etc
```
I think that's a lot overhead running a separate quarkus app per agent
is there any best practices in terms of setting up just one single quarkus app supporting multiple AgentCards and JSONRPC Handler endpoints?
is there any reference architecture for a typical A2A production deployment?
Contributor guide
Assessment
This issue has not been assessed yet.