[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5140":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":18,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":10,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":21,"hasPages":21,"topics":23,"createdAt":10,"pushedAt":10,"updatedAt":41,"readmeContent":42,"aiSummary":43,"trendingCount":16,"starSnapshotCount":16,"syncStatus":44,"lastSyncTime":45,"discoverSource":46},5140,"connect","redpanda-data\u002Fconnect","redpanda-data","Fancy stream processing made operationally mundane","https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fabout\u002F",null,"Go",8678,944,112,175,0,1,3,20,39.93,false,"main",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"amqp","cqrs","data-engineering","data-ops","etl","event-sourcing","go","golang","kafka","logs","message-bus","message-queue","nats","rabbitmq","stream-processing","stream-processor","streaming-data","2026-06-12 02:01:09","Redpanda Connect\n================\n\n[![Build Status][actions-badge]][actions-url]\n\nAPI for Apache V2 builds: [![godoc for redpanda-data\u002Fconnect ASL][godoc-badge]][godoc-url-apache]\n\nAPI for Enterprise builds: [![godoc for redpanda-data\u002Fconnect RCL][godoc-badge]][godoc-url-enterprise]\n\nRedpanda Connect is a high performance and resilient stream processor, able to connect various [sources][inputs] and [sinks][outputs] in a range of brokering patterns and perform [hydration, enrichments, transformations and filters][processors] on payloads.\n\nIt comes with a [powerful mapping language][bloblang-about], is easy to deploy and monitor, and ready to drop into your pipeline either as a static binary or docker image, making it cloud native as heck.\n\nRedpanda Connect is declarative, with stream pipelines defined in as few as a single config file, allowing you to specify connectors and a list of processing stages:\n\n```yaml\ninput:\n  gcp_pubsub:\n    project: foo\n    subscription: bar\n\npipeline:\n  processors:\n    - mapping: |\n        root.message = this\n        root.meta.link_count = this.links.length()\n        root.user.age = this.user.age.number()\n\noutput:\n  redis_streams:\n    url: tcp:\u002F\u002FTODO:6379\n    stream: baz\n    max_in_flight: 20\n```\n\n### !NEW! Check Out the Latest AI Goodies\n\n[Claude Plugin for Redpanda Connect Configs](.\u002F.claude-plugin\u002FREADME.md)\n\nMCP Demo:\n\n[![MCP Demo](https:\u002F\u002Fimg.youtube.com\u002Fvi\u002FJhF8HMpVmus\u002F0.jpg)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=JhF8HMpVmus)\n\nAgentic AI Demo:\n\n[![Agentic AI Demo](https:\u002F\u002Fimg.youtube.com\u002Fvi\u002Foi8qgtTqQRU\u002F0.jpg)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=oi8qgtTqQRU)\n\n### Delivery Guarantees\n\nDelivery guarantees [can be a dodgy subject](https:\u002F\u002Fyoutu.be\u002FQmpBOCvY8mY). Redpanda Connect processes and acknowledges messages using an in-process transaction model with no need for any disk persisted state, so when connecting to at-least-once sources and sinks it's able to guarantee at-least-once delivery even in the event of crashes, disk corruption, or other unexpected server faults.\n\nThis behaviour is the default and free of caveats, which also makes deploying and scaling Redpanda Connect much simpler.\n\n## Supported Sources & Sinks\n\nAWS (DynamoDB, Kinesis, S3, SQS, SNS), Azure (Blob storage, Queue storage, Table storage), GCP (Pub\u002FSub, Cloud storage, Big query), Kafka, NATS (JetStream, Streaming), NSQ, MQTT, AMQP 0.91 (RabbitMQ), AMQP 1, Redis (streams, list, pubsub, hashes), Cassandra, Elasticsearch, HDFS, HTTP (server and client, including websockets), MongoDB, SQL (MySQL, PostgreSQL, Clickhouse, MSSQL), and [you know what just click here to see them all, they don't fit in a README][about-categories].\n\n## Documentation\n\nIf you want to dive fully into Redpanda Connect then don't waste your time in this dump, check out the [documentation site][general-docs].\n\nFor guidance on building your own custom plugins in Go check out [the public APIs](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fredpanda-data\u002Fbenthos\u002Fv4\u002Fpublic\u002Fservice).\n\n## Install\n\nInstall on Linux:\n\n```shell\ncurl -LO https:\u002F\u002Fgithub.com\u002Fredpanda-data\u002Fredpanda\u002Freleases\u002Flatest\u002Fdownload\u002Frpk-linux-amd64.zip\nunzip rpk-linux-amd64.zip -d ~\u002F.local\u002Fbin\u002F\n```\n\nOr use Homebrew:\n\n```shell\nbrew install redpanda-data\u002Ftap\u002Fredpanda\n```\n\nOr pull the docker image:\n\n```shell\ndocker pull docker.redpanda.com\u002Fredpandadata\u002Fconnect\n```\n\nFor more information check out the [getting started guide][getting-started].\n\n## Run\n\n```shell\nrpk connect run .\u002Fconfig.yaml\n```\n\nOr, with docker:\n\n```shell\n# Using a config file\ndocker run --rm -v \u002Fpath\u002Fto\u002Fyour\u002Fconfig.yaml:\u002Fconnect.yaml docker.redpanda.com\u002Fredpandadata\u002Fconnect run\n\n# Using a series of -s flags\ndocker run --rm -p 4195:4195 docker.redpanda.com\u002Fredpandadata\u002Fconnect run \\\n  -s \"input.type=http_server\" \\\n  -s \"output.type=kafka\" \\\n  -s \"output.kafka.addresses=kafka-server:9092\" \\\n  -s \"output.kafka.topic=redpanda_topic\"\n```\n\n## Monitoring\n\n### Health Checks\n\nRedpanda Connect serves two HTTP endpoints for health checks:\n- `\u002Fping` can be used as a liveness probe as it always returns a 200.\n- `\u002Fready` can be used as a readiness probe as it serves a 200 only when both the input and output are connected, otherwise a 503 is returned.\n\n### Metrics\n\nRedpanda Connect [exposes lots of metrics][metrics] either to Statsd, Prometheus, a JSON HTTP endpoint, [and more][metrics].\n\n### Tracing\n\nRedpanda Connect also [emits open telemetry tracing events][tracers], which can be used to visualise the processors within a pipeline.\n\n## Configuration\n\nRedpanda Connect provides lots of tools for making configuration discovery, debugging and organisation easy. You can [read about them here][config-doc].\n\n## Build\n\nBuild with Go (any [currently supported version](https:\u002F\u002Fgo.dev\u002Fdl\u002F)):\n\n```shell\ngit clone git@github.com:redpanda-data\u002Fconnect\ncd connect\ntask build:all\n```\n\n## Formatting and Linting\n\nRedpanda Connect uses [golangci-lint][golangci-lint] for formatting and linting.\n\n- `task fmt` to format the codebase,\n- `task lint` to lint the codebase.\n\nConfigure your editor to use `gofumpt` as a formatter, see the instructions for different editors [here](https:\u002F\u002Fgithub.com\u002Fmvdan\u002Fgofumpt#installation). \n\n## Plugins\n\nIt's pretty easy to write your own custom plugins for Redpanda Connect in Go, for information check out [the API docs][godoc-url], and for inspiration there's an [example repo][plugin-repo] demonstrating a variety of plugin implementations.\n\n## Extra Plugins\n\nBy default Redpanda Connect does not build with components that require linking to external libraries, such as the `zmq4` input and outputs. If you wish to build Redpanda Connect locally with these dependencies then set the build tag `x_benthos_extra`:\n\n```shell\n# With go\ngo install -tags \"x_benthos_extra\" github.com\u002Fredpanda-data\u002Fconnect\u002Fv4\u002Fcmd\u002Fredpanda-connect@latest\n\n# Using task\nTAGS=x_benthos_extra task build:all\n```\n\nNote that this tag may change or be broken out into granular tags for individual components outside of major version releases. If you attempt a build and these dependencies are not present you'll see error messages such as `ld: library not found for -lzmq`.\n\n## Docker Builds\n\nThere's a multi-stage `Dockerfile` for creating a Redpanda Connect docker image which results in a minimal image from scratch. You can build it with:\n\n```shell\ntask docker:all\n```\n\nThen use the image:\n\n```shell\ndocker run --rm \\\n\t-v \u002Fpath\u002Fto\u002Fyour\u002Fbenthos.yaml:\u002Fconfig.yaml \\\n\t-v \u002Ftmp\u002Fdata:\u002Fdata \\\n\t-p 4195:4195 \\\n\tdocker.redpanda.com\u002Fredpandadata\u002Fconnect run \u002Fconfig.yaml\n```\n\n## Contributing\n\nContributions are welcome! To prevent CI errors, please always make sure a pull request has been:\n\n- Unit tested with `task test`\n- Linted with `task lint`\n- Formatted with `task fmt`\n\nNote: most integration tests need to spin up Docker containers, so they are skipped by `task test`. You can trigger\nthem individually via `go test -run \"^Test.*Integration.*$\" .\u002Finternal\u002Fimpl\u002F\u003Cconnector directory>\u002F...`.\n\n[inputs]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fcomponents\u002Finputs\u002Fabout\n[about-categories]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fabout#components\n[processors]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fcomponents\u002Fprocessors\u002Fabout\n[outputs]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fcomponents\u002Foutputs\u002Fabout\n[metrics]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fcomponents\u002Fmetrics\u002Fabout\n[tracers]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fcomponents\u002Ftracers\u002Fabout\n[config-interp]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fconfiguration\u002Finterpolation\n[streams-api]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fguides\u002Fstreams_mode\u002Fstreams_api\n[streams-mode]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fguides\u002Fstreams_mode\u002Fabout\n[general-docs]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fabout\n[bloblang-about]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fguides\u002Fbloblang\u002Fabout\n[config-doc]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fconfiguration\u002Fabout\n[releases]: https:\u002F\u002Fgithub.com\u002Fredpanda-data\u002Fconnect\u002Freleases\n[plugin-repo]: https:\u002F\u002Fgithub.com\u002Fredpanda-data\u002Fredpanda-connect-plugin-example\n[getting-started]: https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-connect\u002Fguides\u002Fgetting_started\n\n[godoc-badge]: https:\u002F\u002Fpkg.go.dev\u002Fbadge\u002Fgithub.com\u002Fredpanda-data\u002Fbenthos\u002Fv4\u002Fpublic\n[godoc-url]: https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fredpanda-data\u002Fbenthos\u002Fv4\u002Fpublic\n[godoc-url-apache]: https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fredpanda-data\u002Fconnect\u002Fpublic\u002Fbundle\u002Ffree\u002Fv4\n[godoc-url-enterprise]: https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fredpanda-data\u002Fconnect\u002Fpublic\u002Fbundle\u002Fenterprise\u002Fv4\n[actions-badge]: https:\u002F\u002Fgithub.com\u002Fredpanda-data\u002Fconnect\u002Factions\u002Fworkflows\u002Ftest.yml\u002Fbadge.svg\n[actions-url]: https:\u002F\u002Fgithub.com\u002Fredpanda-data\u002Fconnect\u002Factions\u002Fworkflows\u002Ftest.yml\n\n[golangci-lint]: https:\u002F\u002Fgolangci-lint.run\u002F\n[jaeger]: https:\u002F\u002Fwww.jaegertracing.io\u002F\n","Redpanda Connect 是一个高性能且弹性的流处理器，能够连接多种数据源和目标，并支持消息的转换、丰富、过滤等处理。项目采用Go语言开发，具备强大的映射语言，易于部署与监控，既可作为静态二进制文件也可通过Docker镜像运行，非常适合云原生环境。它支持声明式配置，用户可以通过简单的YAML文件定义复杂的流处理管道。此外，Redpanda Connect 提供了广泛的集成选项，包括AWS、Azure、GCP等多个云服务以及Kafka、NATS等多种消息队列系统，适用于需要高效处理实时数据流的各种应用场景，如日志处理、事件驱动架构及ETL作业等。",2,"2026-06-11 03:02:42","top_language"]