ParticleDB

“Given how bad your LLM was at bugfixing in the releases tested by Jepsen, I would expect the redesigned version to bring back all those bugs and then some.”

“strong evidence that "the abstraction layer just moved up" mindset”

“Unless someone tells me otherwise, I assume ParticleDB is fake.”

“failing a jepsen test this badly is not the start of something”

“Amateur vibe coders who raised a $60M Series B a few months ago.”

“Makes you wonder if they asked their agent to formally prove it with TLA+ and it just responded that it had performed the proofing.”

“raise 50m to crack that pesky "consistent read after write" nut”

“it takes a lot of of human hubris and incompetence to think you can herd AI agents to squirt out a better version”

“I struggle to imagine how an organization which is capable of taking things seriously would have produced software with these issues to begin with.”

“would behave as immediately illogically as the database under test here.”

“should you have done that in the first place? its a database engine”

“The source being closed, with no QA, what do you expect.”

“Could not find much analysis on it at all which is not the best sign.”

“This thing looks so bad bro I can't help but think this kind of assertion only adds fuel to the fire.”

“The fact that they then said they addressed the issues, but didn't, is about the biggest red flag imaginable.”

“Imagine bringing in any outside testing before your WHERE implementation works.”

“What ParticleDB delivered is so far past good or bad, it's just straight ugly and then some.”

“they very clearly didn't do even the most rudimentary testing”

“none of those builds should have seen the light of day, given all the problems that were found”

“they lack the judgement and engineering competence to credibly provide a database server”

“such as by outright lying to people, then you deal with the consequences”

“Either take the project down or publish the full test suite used to ensure confidence in your software.”

“Our findings suggest structural deficiencies in the ParticleDB QA process.”

“the bold claims they had on their website is what makes this a bust”

“Its also faster than Redis for KV, also numbers show this should be top on clickbench”

“It takes gumption to build a new storage engine.”

“why did this supposedly ACID db have so many issues around its most basic properties?”

“after reading this I would never touch a piece of software built by anyone involved with this”

“We've also fixed the issues highlighted in the report through newer releases”

“It makes mongodb from the report a decade ago look good”

“during our collaboration no TLA+ specification was available.”

“A codebase with that many fundamental issues suggests either no integration tests were written”

“Shipping a bug like "WHERE 4 = 5" returning rows says it all to me”

“However, during our collaboration no TLA+ specification was available.”

“The database was so janky that it sounds like most of the time was spent on basic bugs”

“This is like paying for a pentest of a treehouse, and claiming that this implies the updated treehouse with a working padlock”

“The engine has since been redesigned and all of these issues have been fixed”

“is just something an LLM thought would sound good on a DB’s website”

“It's wild how bad it is. Not surprising for a vibecoded database”

“We present 96 issues in ParticleDB, ranging from the pedestrian (crashes, deadlocks, data loss, etc.)”