How dtkmn/rtb-ingress-benchmark works
RTB Ingress Benchmark Harness compares HTTP receiver implementations under HTTP-only, enqueue, and Kafka-confirmed delivery modes. The principal workflow is k6 load generation against receiver lanes, which validate bid requests and—in Kafka modes—publish them to Kafka; benchmark runs produce results that can be selectively promoted to the published dashboard. README documents the receiver/Kafka scenario and published-snapshot policy. Receiver internals and the downstream sinker/storage wiring are only partly sampled, so those relationships are not inferred here.
Main entry points: services Ingress Lanes · load-test.js Load Generator · main.rs Rust Receiver · published-snapshots.json Published Snapshots
Components 18
Benchmarking
- Load Generator
k6/load-test.js
Receiver Services
- Ingress Lanes
services - Rust Receiver
services/rust-receiver/src/main.rs - Go Receiver
services/go-receiver - Node Receiver
services/node-receiver/src/app.js - Python Receiver
services/python-receiver/app/main.py - Quarkus Receiver
services/quarkus-receiver - Spring Receiver
services/spring-receiver - Spring VT Receiver
services/spring-virtual-receiver
Streaming
- Kafka
- Quarkus Sinker
services/quarkus-sinker - PostgreSQL
Results And Dashboard
- Run Results
results - Published Snapshots
site/src/data/published-snapshots.json - Benchmark Dashboard
site/src/data/site-data.json
Other components
- Prometheus
- Grafana
- Jaeger
Connections 4
- Load Generator → Ingress Lanes: loads
README.md - Ingress Lanes → Kafka: publishes valid bids
README.md - Published Snapshots → Benchmark Dashboard: selects snapshots
README.md - Rust Receiver → Kafka: publishes bids
services/rust-receiver/src/main.rs