Recent submissions

Comment · 9 months ago
Comment · 1 year ago
Hi! You can find the detailed differences here: https://docs.timeplus.com/proton-oss-vs-enterprise

In short, Proton focuses on simplicity — it’s a single-instance engine powerful enough for most common streaming and analytics workflows.

Features like clustering, mutable streams, and S3-based stream storage/state checkpoints are part of the enterprise edition, while Proton keeps the core performance and streaming capabilities in an open-source form.

Comment · 1 year ago
Dynamic Tables are interesting for declarative streaming. In the ClickHouse ecosystem, you might want to look at materialized views combined with streaming engines.

For real-time transformations, there are a few approaches: - Native ClickHouse MaterializedViews with AggregatingMergeTree - Stream processors that write to ClickHouse (Flink, Spark Streaming) - Streaming SQL engines that can read/write ClickHouse

We've been working on streaming SQL at Proton (github.com/timeplus-io/proton) which handles similar use cases - continuous queries that maintain state and can write results back to ClickHouse. The key difference from Dynamic Tables is handling unbounded streams vs micro-batches.

What's your specific use case? Happy to discuss the tradeoffs.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton