←back to thread

/dev/null is an ACID compliant database

(jyu.dev)
529 points swills | 6 comments | 23 Oct 25 21:28 UTC | HN request time: 0s | source | bottom
Show context
gchamonlive ◴[23 Oct 25 23:09 UTC] No.45688632[source]▶
Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.
replies(6): >>45688742 #>>45689108 #>>45690925 #>>45693439 #>>45694805 #>>45695900 #
1. nomel ◴[24 Oct 25 00:03 UTC] No.45689108[source]▶
I've never had a single issue with any user after moving our databases to /dev/null.
replies(2): >>45689758 #>>45695700 #
2. PlunderBunny ◴[24 Oct 25 01:36 UTC] No.45689758[source]▶
Did you route the support requests to /dev/null as well?
replies(2): >>45690072 #>>45690517 #
3. lgas ◴[24 Oct 25 02:25 UTC] No.45690072[source]▶
This is how a lot of big tech companies scale support.
4. soraminazuki ◴[24 Oct 25 03:40 UTC] No.45690517[source]▶
Haha, I guess support.google.com is an ACID compliant database as well.
replies(1): >>45691059 #
5. masklinn ◴[24 Oct 25 05:23 UTC] No.45691059{3}[source]▶
My /dev/null of choice is https://github.com/orgs/community/discussions/
6. crusty_jpeg ◴[24 Oct 25 15:35 UTC] No.45695700[source]▶
It's great. We saw a 2000% throughput increase on our business analytics platform when we switched to a /dev/null backend.