From 6e46ce6e7f95a8cd309d6d2c9213551eda26860a Mon Sep 17 00:00:00 2001 From: alex Date: Tue, 14 Apr 2026 16:56:16 +0000 Subject: Remove Markdown link --- .../tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'blog/content') diff --git a/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi b/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi index daf5329e..01fc5fae 100644 --- a/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi +++ b/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi @@ -20,7 +20,7 @@ Imagine you could write an UI element that subscribed to the following publicati create publication foo for table chat_messages where (channel in :list_of_channels_user_is_in and posted > :some_time_ago); ``` -Without writing any additional code, the UI element would get instantly notified not only of all new messages, but also of editions, deletions, or messages moved in or out of the subscribed channels. I believe you could write a real-time UI element with much shorter and safer code than any alternative I can think of that only uses OSS code. (As far as I know, [ksqlDB](https://github.com/confluentinc/ksql) does a similar thing, but has non-OSS bits and seems much harder to deploy than PostgreSQL, besides you would also need to deploy PostgreSQL.) +Without writing any additional code, the UI element would get instantly notified not only of all new messages, but also of editions, deletions, or messages moved in or out of the subscribed channels. I believe you could write a real-time UI element with much shorter and safer code than any alternative I can think of that only uses OSS code. (As far as I know, ksqlDB does a similar thing, but has non-OSS bits and seems much harder to deploy than PostgreSQL, besides you would also need to deploy PostgreSQL.) This has some caveats: -- cgit v1.2.3