Gallery
About
While building an IoT telemetry solution, we ran into hurdles with Clickhouse. For one, you can't insert quickly AND durably into Clickhouse without setting up something like Kafka, which gets complicated for quick projects wanting to make use of Clickhouse's powerful features. Then, trying to actually query Clickhouse and show data in a UI required a whole backend API to handle auth and permissions.We figured that all these parts together – fast, durable ingest, row-level and column-level security and roles, and realtime streaming – were a lot of scaffolding to have to rebuild for every project we wanted to use Clickhouse in. So, we built them all into a single Go binary to be deployed alongside Clickhouse, to help lower Clickhouse's barrier to entry. We call it WaveHouse.Would love any feedback as we work on improving and adding more features to this OSS project!
Comments (3)
skipping kafka is bold. throughput numbers vs standard pipeline?
ClickHouse forcing Kafka for durable inserts was absurd anyway.
how do you handle write durability without kafka buffering?
Related Products
Free Currency Converter API
Limestone Digital
AI-Powered Software Development, Engineering Team Augmentation,
ChangeSpec
Free Mermaid Live Editor & Diagram Maker
MobileGym: A Verifiable and Highly Parallel Simulation Platform for Mobile GUI A
Universal Data Workbench
A thorough tool for cleaning, validating, and converting JSON, CSV, and more.
ComingUp