enether

6 ms·

31.
by enether 9mo ago
+1. Bluesky is a left-leaning political mess - I strictly follow tech-only accounts yet get posts on the timeline about what this week's monstrous White House act was. This is not a judgement against the left, but rather against Bluesk
32.
by enether 9mo ago
I didn't use AI in writing the post. I did some research with it, and used it to help create the ASCII art a bit. That's about it. I was afraid that adding the emoji would trigger someone to think it's AI. In any case, nowada
33.
by enether 9mo ago
yes. apparently before Dec 19 too
34.
by enether 9mo ago
I was definitely unaware. I suspected something like this may be up when I talked about the zero-review of the apparent PR "I’m not aware of Mongo’s public review practices". This is great to know though. Updating the piece now to
35.
by enether 9mo ago
thanks! updated
36.
by enether 9mo ago
What an awful vulnerability. The most interesting fact is that this has been there since the PR that introduced it in 2017[1]. I'm not sure how Mongo's review process works, but it seems like this one had zero review. [1] - https
37.
by enether 10mo ago
Warpstream (by Confluent (an IBM company))
38.
by enether 10mo ago
For Rust-based Kafka alternatives, I like Tansu[1]. It at least provides Kafka API parity, and critically also gives users a pluggable backend (embedded SQLite, S3 for low cost diskless type workloads and Postgres because just use Postgres)
39.
by enether 11mo ago
That is hilarious. The product looks like garbage to me. The business opportunity looks like it can be incredibly lucrative if it does catches on.
40.
by enether 11mo ago
Aren't nanoplastics a larger concern? All microplastics out in the open will degrade to nanoplastics at some point, and those find it much easier to infiltrate the human body. They penetrate the blood-brain barrier. This leads me to be
41.
Kafka is Topping Out (as a business)(bigdata.2minutestreaming.com)
2 points by enether 11mo ago|0 comments
42.
by enether 11mo ago
how is node failure handled? is this using KRaft or ZK?
43.
by enether 11mo ago
These are real trade offs! Client impl. can be re-created once in a library/extension and be done with. The network effect of Kafka is the hardest to topple. The API is standard. If you need that connectivity, then use Kafka. An altern
44.
by enether 11mo ago
Exactly. "a properly-configured Kafka cluster" implies you have very properly configured your clients too, which is almost never the case because it's practically very hard to do in the messy reality of a large-scale organiza
45.
by enether 11mo ago
Can you give some examples? I'm super curious about single-node Kafka use cases in general
46.
by enether 11mo ago
I believe most setups using DB+{Queue,Kafka} don't truly deal with it fwiw.
47.
by enether 11mo ago
Agree but we really have to put a number on baseline traffic and max traffic burst in order to be productive in the discussion. I would argue that the majority of use cases never need to be designed for a max-traffic-number that PG can&#x27
48.
by enether 11mo ago
+1 on connections being the limiting factor. Curious how further a connection pooler can get you
49.
by enether 11mo ago
The key question here is what is "high sustained rate" in numbers?
50.
by enether 11mo ago
My understanding is this is pretty niche and can be complex.
51.
by enether 11mo ago
Do I understand it correctly that DuckDB would run embedded on the machine running Postgres (i.e through the extension), and this limits query processing ability to whatever that machine can comfortably handle? What are the deployment impli
52.
by enether 11mo ago
What does "remotely" mean in this context? My understanding is that all of this runs on the same machine - your Postgres server machine runs DuckDB on the same machine via the extension. I assume you simply mean DuckDB, being a co
53.
by enether 11mo ago
but most serious compute engines already speak Iceberg, what do they gain from interfacing with PG now? My understanding is the opposite - PG cuts it as a compute layer for small amounts of data, and this is where it excels. I also assume `
54.
by enether 11mo ago
yeah, this exchange reads like a sales ad
55.
No one will tell you the real cost of Kafka (2024)(blog.2minutestreaming.com)
2 points by enether 11mo ago|0 comments
56.
by enether 11mo ago
This is the crux of my point. Postgres is the solution in question of the article because I simply assume the majority of companies will start with Postgres as their first piece of infra. And it is often the case. If not - MySQL, SQLite, wh
57.
by enether 11mo ago
I also strongly believe it's not a headache. Vendors frequently push that narrative so they can sell their own managed (or proprietary) solution on it. With a decent AI model (e.g ChatGPT Pro), it's easier than ever to figure out
58.
by enether 11mo ago
yeah, this was my intention. I have no real way of knowing if it truly covers 80% of use cases, or 70%, or 40%, anyway.
59.
by enether 11mo ago
That's true. There seems to be two planes of ease of use - the app layer (library) and the infra layer (hosting). The app layer for Postgres is still in development, so if you currently want to run pub-sub (Kafka) on it, it will be ext
60.
by enether 11mo ago
hehe, yeah it is. I could have probably got a GB/s out of that if I ran it properly - but it's at the scale where you expect it to be terrible due to the mismatch of workloads

More ›