Live data from Hacker News

/dev/null is an ACID compliant database

jyu.dev

91–100 of 203 posts

Re: /dev/null is an ACID compliant database

#93

Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.

WTF is going on with the issues and pull requests for that repo?

This commit is interesting, it used to support /dev/null natively, but for the sake of supporting windows you now have to use /dev/null externally by writing nothing at all

https://github.com/kelseyhightower/nocode/commit/80f38e0f103...

Re: /dev/null is an ACID compliant database

#95

I've used /dev/null for exactly this purpose. I have output that needs to go somewhere, and I don't want to worry about whether that somewhere can handle it. Later on in deployment, it will go somewhere else. Somewhere that has been evaluated for being able to handle it. In that way, /dev/null is to storage what `true` is to execution - it just works.

Bug free software is a pipe dream, but if there is anything I've never encountered any bugs with, /dev/null and true is certainly in the top 3.

Ah you've never encountered /dev/null not existing yet, so when you try to trash data it will actually create a normal file there so every other program that uses it will actually append that file.

Luckily it's usually a tmpfs

Re: /dev/null is an ACID compliant database

#96

Earlier quoted context omitted.

I usually do a kubernetes cluster on top of VMs. But sometimes when I really want to scale the standard cloud server less platforms all support /dev/null out of the box. (Except for Windows...)

> Except for Windows... copy c:\file nul It's been there since DOS or more likely CP/M :)

Still need an adapter library though! Fortunately there are about 7 competing implementations on npm and most of them only have 5-6 transitive dependencies.

Re: /dev/null is an ACID compliant database

#98
post #50

Earlier quoted context omitted.

I've never had a single issue with any user after moving our databases to /dev/null.

Did you route the support requests to /dev/null as well?

Haha, I guess support.google.com is an ACID compliant database as well.
Post reply on HN