Top all-time · #6386
Decodable
Company blog · decodable.co/blogdataprogramming
Decodable is the company blog at decodable.co, writing about data and programming. Since 2022, 12 different Hacker News readers have linked it 26 times, most often “Revisiting the Outbox Pattern”. It is still writing: the last post was on 2025-07-28, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link Decodable's blog on Postgres change data capture, replication slots and event-driven architecture, including its post on the dual nature of events.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Powered by Apache Flink® and Debezium, Decodable provides a fast, easy, yet powerful stream processing platform free from the pain, time, and cost of assembling the individual components.
Most-linked posts?
- Revisiting the Outbox Pattern5 people · 5 mentions · first linked 2024-10-31
- Logical Replication from Postgres 16 Stand-By Servers3 people · 3 mentions · first linked 2023-12-19
- Failover Replication Slots with Postgres 172 people · 3 mentions · first linked 2024-12-03
- "Change Data Capture Breaks Encapsulation". Does It, Though?2 people · 2 mentions · first linked 2023-11-21
What Hacker News says?
Things got finally a bit easier with Postgres 16, which allows you to create replication slots on stand-by servers. It still requires manual intervention to make sure they don't fall too far behind their primary counterpart and to do the failover, but it's not too terrible either and it's guaranteed that failover can happen without missing any events. I've described the approach here: https://www.decodable.co/blog/l…
Comment linking /blog/logical-replication-from-postgres-16-stand-by-servers-part-2-of-2
on “Show HN: Peerdb Streams – Simple, native Postgres change data capture”Submitted Revisiting the Outbox Pattern as a story · 6 points
HN discussionNice one. I wrote about this a while ago, from a slightly different perspective, focusing on data change events [1]. Making a similar differentiation there between id-only events (which you describe as triggers of action; from a data change feed perspective, that action typically would be a re-select of the current state of the represented record), full events (your carriers of data) and patch events (carriers of da…
Comment linking /blog/taxonomy-of-data-change-events
on “The Dual Nature of Events in Event-Driven Architecture”Submitted We’re Abusing the Data Warehouse; RETL, ELT, and Other Weird Stuff as a story · 4 points
HN discussionOne way for addressing this concern is (stateful) stream processing, for instance using Kafka Streams of Apache Flink: using a state store, you ingest the CDC streams for all the tables and incrementally update joins between them whenever there's an event coming in for either input stream. Touched on this recently in this talk about streaming data contracts: https://speakerdeck.com/gunnarmorling/data-contracts-in-pr…
Comment linking /blog/taxonomy-of-data-change-events
on “How to stream PostgreSQL CDC to Kafka and use Propel to get an instant API”Submitted "Change Data Capture Breaks Encapsulation". Does It, Though? as a story · 3 points
HN discussionSubmitted Exploring Flink CDC as a story · 2 points
HN discussionSubmitted Failover Replication Slots with Postgres 17 as a story · 2 points
HN discussionSubmitted Revisiting the Outbox Pattern as a story · 2 points
HN discussionSubmitted Revisiting the Outbox Pattern as a story · 2 points
HN discussionSubmitted Revisiting the Outbox Pattern as a story · 2 points
HN discussionSubmitted Flink SQL–Misconfiguration, Misunderstanding, and Mishaps as a story · 2 points
HN discussionSubmitted A Taxonomy of Data Change Events as a story · 2 points
HN discussionSubmitted Logical Replication from Postgres 16 Stand-By Servers as a story · 2 points
HN discussionSubmitted The Wonders of Postgres Logical Decoding Messages for CDC as a story · 2 points
HN discussionSubmitted "Change Data Capture Breaks Encapsulation". Does It, Though? as a story · 2 points
HN discussionSubmitted Apache Flink Deployments at Decodable as a story · 2 points
HN discussionSubmitted Decodable is GA – Real-time stream processing in SQL in the cloud as a story · 2 points
HN discussionSubmitted Failover Replication Slots with Postgres 17 as a story · 1 points
HN discussionSubmitted Revisiting the Outbox Pattern as a story · 1 points
HN discussionSubmitted Failover Replication Slots with Postgres 17 as a story · 1 points
HN discussionSubmitted Why Do I Need Change Data Capture (CDC) as a story · 1 points
HN discussionSubmitted Logical Replication from Postgres 16 Standby as a story · 1 points
HN discussionSubmitted Logical Replication from Postgres 16 Stand-By Servers as a story · 1 points
HN discussionSubmitted Getting Started with PyFlink on Kubernetes as a story · 1 points
HN discussionSubmitted Postgres 15: Logical Decoding Row Filters with Debezium (2022) as a story · 1 points
HN discussion
