I'm not even sure what the "bug" in the title refers to, other than serving as clickbait.
How is this different from Postgres + PGBouncer? They decouple the connections from the the work of the database server itself, which can interleave transactions between connections to one connection to Postgres.
The article also mentions comparing against Redis "before 6.0"; 3 major versions behind.
It's fine to do marketing posts about your product, but I don't come away from this with strong signal for rigor.
I'm not even sure what the "bug" in the title refers to, other than serving as clickbait.
How is this different from Postgres + PGBouncer? They decouple the connections from the the work of the database server itself, which can interleave transactions between connections to one connection to Postgres.
The article also mentions comparing against Redis "before 6.0"; 3 major versions behind.
It's fine to do marketing posts about your product, but I don't come away from this with strong signal for rigor.
It seems to be a vibe coded database product they are selling.
Seems like a vibe first then try to find a use for it later kind of project.
I support indie devs 100% but also the article is not very interesting.
They need better stuff to catch people's attention.