Redpanda Connect

go · stream-processor · BUSL-1.1 · planned · go

Homepage · Source · Its configuration in this repository

Has this configuration been reviewed upstream?

Not yet. This configuration has not been checked by the people who maintain this system, and until it has, treat its numbers as ours rather than theirs.

Why this is not measured yet

It has no native ClickHouse output at all, so the arm goes through `sql_insert` with the Go driver. That is a third distinct insert path — not Native, not RowBinary — and rule 5 requires it appear in the results table, because it is not the same amount of server-side work. Batching defaults to disabled (count, size and period all zero). Running it unbatched would produce a meaninglessly bad number, and publishing that would be the failure rule 2 exists to prevent: a slow competitor arm is a bug in our benchmark, not a result.

Licence gate: BSL 1.1 with a Community Licence over parts of the connector set. Built and run, but numbers stay unpublished until the licence text has been read — specifically whether it constrains publishing comparative benchmark results.

Its arms

No arms are implemented yet.

Where it has been measured

No published measurement carries this system yet.

Tell us we got this wrong

If this system is configured badly here, that is a bug in this benchmark rather than a result about Redpanda Connect, and the pull request that fixes it is the most valuable one this repository can receive. How to send one. The whole configuration is at entrants/redpanda-connect.