This section contains information about the different interfaces for working with the YTsaurus system: HTTP and RPC proxies.

HTTP proxy

HTTP proxy is a universal interface for working with the YTsaurus system.


There are more convenient interfaces for working with the YTsaurus system: Python API and С++ API.

This interface can be useful in one of two cases:

  1. You need to use YTsaurus commands in a browser or console utility (such as curl).
  2. You need to write a layer with abstractions to YTsaurus.

HTTP proxies differ depending on the query type. Queries to the metainformation tree like get or set are considered relatively light and processed by so called control (light) HTTP proxies.
Read or write queries (read-table, write-table) can potentially transfer a significantly larger amount of data, more heavily load YTsaurus cluster nodes, and are therefore processed by so called heavy proxies (data proxies).

An example of user interaction with YTsaurus via the HTTP interface is available in the HTTP proxy section.

For reference information about the HTTP proxy, see HTTP proxy reference.

RPC proxy

RPC proxy is a special interface for interacting with YTsaurus via the RPC protocol. The RPC proxy is accessed via TCP, port 9013. What basically distinguishes the RPC proxy from the HTTP proxy:

  • Higher query processing speed achieved due to the following features:
    • Work with the RPC proxy is performed using a special internal protocol that is better suited for working with a large number of concurrent queries.
    • In the RPC proxy, a query is sent in native YTsaurus format and does not require additional time and resources for conversion.
    • The ability to maintain compatibility at the user code level with changes in the protocol of interaction of components within a YTsaurus cluster.

The following programming languages are supported:

Examples are available for each programming language.

In this article: