Code behind LaserData's Apache Iggy blogs, docs and use-case write-ups, in one place. LaserData builds and runs Apache Iggy, the open-source message streaming platform written in Rust.
- developer-pain/ has one folder per developer problem in the market map's section 02: the kit, example or open-source contribution that proves LaserData's answer.
- use-cases/ has one runnable demo per use case in section 04.
Each folder's README links its blog, doc and posts, says where the code is meant to go (a LaserData repo, or a pull request to another project), and what has not been tested yet.
| # | Problem | Code | Blog, doc and posts |
|---|---|---|---|
| 01 | Latency & p99 spikes | developer-pain/01-latency | Blog · Doc · Posts |
| 02 | Local dev / testing heaviness | developer-pain/02-local-testing | Blog · Doc · Posts |
| 03 | Memory / CPU / JVM / GC | developer-pain/03-resource-footprint | Blog · Doc · Posts |
| 04 | Partition limits & hot partitions | developer-pain/04-partitions | Blog · Doc · Posts |
| 05 | TLS / SASL / auth setup | developer-pain/05-auth | Blog · Doc · Posts |
| 06 | Kubernetes ops & upgrades | developer-pain/06-kubernetes | Blog · Doc · Posts |
| 07 | Consumer-group rebalancing & stalls | developer-pain/07-rebalancing | Blog · Doc · Posts |
| 08 | Lag & observability | developer-pain/08-consumer-lag | Blog · Doc · Posts |
| 09 | Cross-AZ & storage cost | developer-pain/09-cost | Blog · Doc · Posts |
| 10 | Client library maintenance & SDK parity | developer-pain/10-sdks | Blog · Doc · Posts |
| 11 | Exactly-once / transactions | developer-pain/11-delivery-guarantees | Blog · Doc · Posts |
| 12 | Schema registry & serialization | developer-pain/12-schema-registry | Blog · Doc · Posts |
| Use case | Code | Write-up |
|---|---|---|
| Real-time price distribution | use-cases/iggy-market-data-fanout | Write-up |
| Live scores, odds and reactions | use-cases/iggy-live-event-fanout | Write-up |
| Bids, wins and ad budgets | use-cases/iggy-rtb-bidstream | Write-up |
| Courier location, dispatch and ETA | use-cases/iggy-rider-eta | Write-up |
| Live inventory and pricing | use-cases/iggy-inventory-pricing | Write-up |
| Engagement events and real-time triggers | use-cases/iggy-engagement-triggers | Write-up |
| Telemetry and alerting hot tier | use-cases/iggy-telemetry-hot-tier | Write-up |
| An event bus for AI voice and chat agents | use-cases/iggy-agent-bus | Write-up |
| Game telemetry and live-ops | use-cases/iggy-game-telemetry | Write-up |
| Fraud and risk features | use-cases/iggy-fraud-features | Write-up |
| Usage metering and quotas | use-cases/iggy-usage-metering | Write-up |
| Edge store-and-forward | use-cases/iggy-edge-forward | Write-up |
| An order and trade event log | use-cases/iggy-order-event-log | Write-up |
- Nothing here has been run against a live Apache Iggy server yet; each folder lists what was checked (compile, import, unit tests).
- Benchmarks have no published numbers until they are run on real machines.
- No pull requests have been opened in other projects.
The blog, doc and write-up links open pages in the LaserData market map.