> For the complete documentation index, see [llms.txt](https://developer.barchart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.barchart.com/architecture/protobuf.md). # Protobuf A brief background and context of the core architecture behind Barchart's Openfeed Platform The Openfeed service is built on top of Google Protocol Buffers (Protobuf). Protobufs are a language-neutral, platform-neutral, extensible mechanism for serializing structured data. Compacting robust data into a serialized binary format (machine language) allows for faster data transmission. This is important since handling a highly active feed from a global market exchange can send terabytesof data each trading day. It is a highly efficient, binary format that is smaller and faster than alternatives like XML and JSON, making it ideal for high-performance communication --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.barchart.com/architecture/protobuf.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.