<story><title>Show HN: Skor – Drop-in microservice to get Postgres changes as JSON webhooks</title><url>https://github.com/hasura/skor</url></story><parent_chain></parent_chain><comment><author>odammit</author><text>Looks cool. Seems like a good alternative if you can’t use listen&amp;#x2F;notify for some reason.&lt;p&gt;I’ve used listen&amp;#x2F;notify with triggers for a while with good success. The flexibility of my apps controlling what they want to listen for instead of having that config elsewhere.&lt;p&gt;Downside to l&amp;#x2F;n is that if you aren’t listening you aren’t getting changes. Seems like the same is true if the webhook fails here since there isn’t a retry.&lt;p&gt;If you want to check out another cool alternative see Debezium[1]. It’s uses PGs logical decoding feature to stream changes. Supports protobufs and JSON output.&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;debezium.io&amp;#x2F;docs&amp;#x2F;connectors&amp;#x2F;postgresql&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;debezium.io&amp;#x2F;docs&amp;#x2F;connectors&amp;#x2F;postgresql&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Show HN: Skor – Drop-in microservice to get Postgres changes as JSON webhooks</title><url>https://github.com/hasura/skor</url></story><parent_chain></parent_chain><comment><author>pfooti</author><text>Interesting. A quick look at the code indicates you&amp;#x27;re just doing a notify on the whole row. Have you tested with large rows? The postgres notify function fails with a payload larger than 8000 bytes, and that limit cannot be changed at runtime, last I looked.&lt;p&gt;I wrote a similar thing to notify on changes, but had to just fire notifies on what changed (id, column names) and there was a second step in the listening code to fetch the full details.</text></comment>