@stanislavkozlovski.bsky.social
The Android feels choppy/flow and the touch also doesn't feel super responsive
November 11, 2025 at 8:57 PM
The Android feels choppy/flow and the touch also doesn't feel super responsive
Daylight is amazing. I'm really looking forward to a v2 (whenever it comes) that's a bit more refined
November 11, 2025 at 6:51 PM
Daylight is amazing. I'm really looking forward to a v2 (whenever it comes) that's a bit more refined
I mean, yeah - it's not a technical piece, it's a financial article.
When I hear the Kafka community, I think about engineering talk more than anything else
When I hear the Kafka community, I think about engineering talk more than anything else
November 11, 2025 at 6:49 PM
I mean, yeah - it's not a technical piece, it's a financial article.
When I hear the Kafka community, I think about engineering talk more than anything else
When I hear the Kafka community, I think about engineering talk more than anything else
With greater competition and commercialization, it seems bound to happen.
I'm of the opinion we're bound to see consolidation in the space soon, because there's too many companies chasing too little of a market: bigdata.2minutestreaming.com/p/event-stre...
I'm of the opinion we're bound to see consolidation in the space soon, because there's too many companies chasing too little of a market: bigdata.2minutestreaming.com/p/event-stre...
November 10, 2025 at 3:34 PM
With greater competition and commercialization, it seems bound to happen.
I'm of the opinion we're bound to see consolidation in the space soon, because there's too many companies chasing too little of a market: bigdata.2minutestreaming.com/p/event-stre...
I'm of the opinion we're bound to see consolidation in the space soon, because there's too many companies chasing too little of a market: bigdata.2minutestreaming.com/p/event-stre...
Then I don't see why a relational database can't maintain a pending queue too. Just process the lowest-id job
November 8, 2025 at 10:45 PM
Then I don't see why a relational database can't maintain a pending queue too. Just process the lowest-id job
What are you referring to?
My intuition is rather that discussion has somewhat died down, in general.
My intuition is rather that discussion has somewhat died down, in general.
November 8, 2025 at 10:44 PM
What are you referring to?
My intuition is rather that discussion has somewhat died down, in general.
My intuition is rather that discussion has somewhat died down, in general.
re: fairness - I admit I'm not as familiar with. Can you teach me how some of these systems ensure fairness? Do they refuse to give messages to performant workers and hold them off for slower ones?
November 8, 2025 at 2:21 PM
re: fairness - I admit I'm not as familiar with. Can you teach me how some of these systems ensure fairness? Do they refuse to give messages to performant workers and hold them off for slower ones?
There is some fundamental misunderstanding here.
pgmq is not based on top of SQS. It only provides API parity with it. No messages actually go to SQS...
Latency-wise, my tests showed single-digit write and read. 99% use cases don't need less.
pgmq is not based on top of SQS. It only provides API parity with it. No messages actually go to SQS...
Latency-wise, my tests showed single-digit write and read. 99% use cases don't need less.
November 8, 2025 at 2:21 PM
There is some fundamental misunderstanding here.
pgmq is not based on top of SQS. It only provides API parity with it. No messages actually go to SQS...
Latency-wise, my tests showed single-digit write and read. 99% use cases don't need less.
pgmq is not based on top of SQS. It only provides API parity with it. No messages actually go to SQS...
Latency-wise, my tests showed single-digit write and read. 99% use cases don't need less.
I really don't know. I haven't evaluated it yet.
November 8, 2025 at 2:18 PM
I really don't know. I haven't evaluated it yet.
ok, so what is missing?
> move data fairly, fast, and reliably
It is fast. It is reliable.
It is not fair (the simple implementation).
Is fairness the missing piece?
(Just want to streamline the discussion)
> move data fairly, fast, and reliably
It is fast. It is reliable.
It is not fair (the simple implementation).
Is fairness the missing piece?
(Just want to streamline the discussion)
November 8, 2025 at 10:55 AM
ok, so what is missing?
> move data fairly, fast, and reliably
It is fast. It is reliable.
It is not fair (the simple implementation).
Is fairness the missing piece?
(Just want to streamline the discussion)
> move data fairly, fast, and reliably
It is fast. It is reliable.
It is not fair (the simple implementation).
Is fairness the missing piece?
(Just want to streamline the discussion)
100%. I'm replying in facts.
I simply perceived your intro/outro belittling the Postgres argument to clickbait to reach front-page of HN as such, hence fought back.
I simply perceived your intro/outro belittling the Postgres argument to clickbait to reach front-page of HN as such, hence fought back.
November 8, 2025 at 10:05 AM
100%. I'm replying in facts.
I simply perceived your intro/outro belittling the Postgres argument to clickbait to reach front-page of HN as such, hence fought back.
I simply perceived your intro/outro belittling the Postgres argument to clickbait to reach front-page of HN as such, hence fought back.
The problem with building that is that... it exists! github.com/tansu-io/tansu
GitHub - tansu-io/tansu: Apache Kafka® compatible broker with S3, PostgreSQL, SQLite, Apache Iceberg and Delta Lake
Apache Kafka® compatible broker with S3, PostgreSQL, SQLite, Apache Iceberg and Delta Lake - tansu-io/tansu
github.com
November 8, 2025 at 10:03 AM
The problem with building that is that... it exists! github.com/tansu-io/tansu
Pub-sub doesn't exist (much).
So yeah, unless somebody builds the `pgmq` equivalent and makes it work nice enough, it would be extra work that probably isn't justified.
It strongly depends on how much of that "complicated system" you truly need though!
So yeah, unless somebody builds the `pgmq` equivalent and makes it work nice enough, it would be extra work that probably isn't justified.
It strongly depends on how much of that "complicated system" you truly need though!
November 8, 2025 at 10:02 AM
Pub-sub doesn't exist (much).
So yeah, unless somebody builds the `pgmq` equivalent and makes it work nice enough, it would be extra work that probably isn't justified.
It strongly depends on how much of that "complicated system" you truly need though!
So yeah, unless somebody builds the `pgmq` equivalent and makes it work nice enough, it would be extra work that probably isn't justified.
It strongly depends on how much of that "complicated system" you truly need though!
I disagree with your take that it's "complicated". You can write a queue/pub-sub in an hour.
We have to separate the two, though:
- queues exists in battle-tested libraries like pgmq and the older pgq
So this is already built. Unless you want complex routing a-la Rabbit, its fine to use Postgres!
We have to separate the two, though:
- queues exists in battle-tested libraries like pgmq and the older pgq
So this is already built. Unless you want complex routing a-la Rabbit, its fine to use Postgres!
November 8, 2025 at 10:02 AM
I disagree with your take that it's "complicated". You can write a queue/pub-sub in an hour.
We have to separate the two, though:
- queues exists in battle-tested libraries like pgmq and the older pgq
So this is already built. Unless you want complex routing a-la Rabbit, its fine to use Postgres!
We have to separate the two, though:
- queues exists in battle-tested libraries like pgmq and the older pgq
So this is already built. Unless you want complex routing a-la Rabbit, its fine to use Postgres!
I think the blog makes a lot of straw mans and misses the point.
I definitely agree with some points made there and remain reasonable - but I think that under my mentioned constraints, PG is likely the right choice
I posted a rebuttal here if you care enough to read github.com/gunnarmorlin...
I definitely agree with some points made there and remain reasonable - but I think that under my mentioned constraints, PG is likely the right choice
I posted a rebuttal here if you care enough to read github.com/gunnarmorlin...
"You Don't Need Kafka, Just Use Postgres" Considered Harmful - Gunnar Morling · gunnarmorling discussions.morling.dev · Discussion #336
"You Don't Need Kafka, Just Use Postgres" Considered Harmful - Gunnar Morling Looking to make it to the front page of HackerNews? Then writing a post arguing that "Postgres is enough", or why "you ...
github.com
November 3, 2025 at 11:46 PM
I think the blog makes a lot of straw mans and misses the point.
I definitely agree with some points made there and remain reasonable - but I think that under my mentioned constraints, PG is likely the right choice
I posted a rebuttal here if you care enough to read github.com/gunnarmorlin...
I definitely agree with some points made there and remain reasonable - but I think that under my mentioned constraints, PG is likely the right choice
I posted a rebuttal here if you care enough to read github.com/gunnarmorlin...
Well... that would pretty easily be alleviated by just running a separate instance, right? I am not advocating for co-locating it.
In any case, I think one would need to expose some dumbed down API for pub-sub users to avoid them doing more than just using the pub-sub, at least in the apps.
In any case, I think one would need to expose some dumbed down API for pub-sub users to avoid them doing more than just using the pub-sub, at least in the apps.
November 3, 2025 at 10:48 PM
Well... that would pretty easily be alleviated by just running a separate instance, right? I am not advocating for co-locating it.
In any case, I think one would need to expose some dumbed down API for pub-sub users to avoid them doing more than just using the pub-sub, at least in the apps.
In any case, I think one would need to expose some dumbed down API for pub-sub users to avoid them doing more than just using the pub-sub, at least in the apps.
What scale are we talking about here?
November 3, 2025 at 9:45 PM
What scale are we talking about here?
Doesn't sound like a bad idea at all. When you've got close to a billion users, might as well connect them!
November 2, 2025 at 10:11 AM
Doesn't sound like a bad idea at all. When you've got close to a billion users, might as well connect them!
Thanks, it's mine. It comes off this post topicpartition.io/blog/postgre... where I focus on how PG solves so many problems at smaller scale
November 2, 2025 at 9:47 AM
Thanks, it's mine. It comes off this post topicpartition.io/blog/postgre... where I focus on how PG solves so many problems at smaller scale
What has changed since?
October 26, 2025 at 6:57 PM
What has changed since?