Search for a command to run...
Articles tagged with #architecture
Inline every schema and your request and response models drift apart. Extract everything and the document becomes a maze of one-off references. The middle path is a small set of rules for what becomes a component, what stays inline, and how to name and compose it.
Asking an LLM to read your whole codebase and emit OpenAPI produces fluent, non-reproducible fiction. Pure AST scanning is reproducible but goes blind on dynamic serializers. The reliable design is static analysis first, with AI filling only proven gaps a human can review.
You do not need to rewrite a working HTTP service as an agent framework to be reachable over A2A. A thin, stateless adapter can expose one authenticated business handler as JSON-RPC, REST, and native gRPC, while being honest about which agent capabilities it does not provide.
MCP connects one agent to tools and data. A2A connects autonomous agents to each other through discoverable, long-lived tasks. They are not competitors; they sit at different layers, and getting the boundary wrong is where agent architectures become unmaintainable.
Pointing an agent at forty internal MCP servers breaks tool limits and buries it in duplicated names. The pattern that works at scale is one authenticated gateway that aggregates specs, namespaces the tools, and keeps auth, logging, and rate limits in one place.
The same MCP server can run over stdio on a laptop or Streamable HTTP behind a domain, and the choice changes auth, state, latency, and who can use it. Here is a decision framework with the actual launch commands and client config for each transport.
