12h ago · 25 min read · TLDR: Any service that writes to a database and publishes a message in the same logical operation has a dual write problem. try/catch retries don't fix it — they turn failures into duplicates. The Transactional Outbox pattern co-writes business data ...
Join discussion12h ago · 37 min read · A data engineering team at a fintech company built what they believed was a robust Change Data Capture pipeline: three source databases (PostgreSQL, MongoDB, and Cassandra), Debezium connectors wired to Kafka, and a downstream data warehouse receivin...
Join discussion1d ago · 6 min read · To sink Kafka streams to Apache Iceberg with RisingWave: create a Kafka source, build a materialized view to transform or aggregate the data, then create an Iceberg sink pointing to your catalog and table. RisingWave handles continuous writes automat...
Join discussion
1d ago · 5 min read · Apache Iceberg serves as the ideal durable event store for event-driven architectures. Unlike Kafka—which has limited retention and no SQL query interface—Iceberg on S3 retains events indefinitely, supports time travel to replay any historical period...
Join discussion
2d ago · 8 min read · Most engineers who connect RisingWave to a Debezium CDC topic reach for FORMAT DEBEZIUM by default. The name matches the tool, so the choice feels obvious. But for a surprisingly common case, it is the wrong choice, and using it silently trades away ...
Join discussion
3d ago · 11 min read · Introduction You have millions of events flowing through Kafka every minute: orders, clicks, sensor readings, log entries. Somewhere downstream, a product manager refreshes a dashboard and sees data from 15 minutes ago. That gap between event time an...
Join discussion
3d ago · 12 min read · Every product team wants to understand what users do on their site. Which pages do they visit? Where do they drop off? How many actually complete a purchase? Traditional analytics pipelines batch this data overnight, which means you find out about pr...
Join discussion
3d ago · 13 min read · Event-driven microservices promise loose coupling and real-time responsiveness. In practice, they deliver something else: hundreds of lines of consumer boilerplate, hand-rolled state management, and retry logic that nobody wants to maintain. If you h...
Join discussion
3d ago · 5 min read · There's a moment when you're building a backend where you realize that not everything needs to happen immediately. A user uploads a video — do they need to wait 2 minutes for it to be transcoded befor
Join discussion
