Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

/dev/null is an ACID compliant database

jyu.dev

Post reply on HN
Print view View original

61–70 of 203 posts

Re: /dev/null is an ACID compliant database

#61

Post by inopinatus »

cluckindan wrote: post #2

Always instantly consistent, always available, and perfectly tolerant of partitioning. Truly, it is the only database which can be scaled to unlimited nodes and remain fully CAP.

Enterprise DBAs will nevertheless provision separate /dev/null0 and /dev/null1 devices due to corporate policy. In the event of an outage, the symlink from null will be updated manually following an approved run book. Please note that this runbook must be revalidated annually as part of the sarbox audit, without which the null device is no longer authorised for production use and must be deleted

Re: /dev/null is an ACID compliant database

#64

Post by latexr »

1718627440 wrote: post #53
noir_lord wrote: post #22

Earlier quoted context omitted.

Joking aside I can’t ever remember seeing a bug in either bash or zsh, never seen either crash or segfault and anytime I’ve had weirdness it’s always turned out to be me missing something. Both (along with a lot of the standard utilities) are a testament to what talented C programmers plus years of people beating on them in unintended ways can achieve in terms of reliability/stability.

Programs not outputting a final newline to stdout leave a prompt that doesn't start on column 0, and readline seams to not takes this into consideration, but still optimizes redraws and overwrites so you get an inconsistent display. This bugs seam to exist in a lot of shells and interactive programs. The program causing the issue isn't POSIX conform though.

> seams

The correct spelling is “seems”. I first assumed it was a typo, but since you did it twice I thought you might like to know.

Re: /dev/null is an ACID compliant database

#66

Post by voidfunc »

charcircuit wrote: post #51
chrisweekly wrote: post #49

Earlier quoted context omitted.

seems you've missed the joke

It's not a funny one if it was one. Of course something is going to be a bad database if it's not a database.

"Its not funny" says the one guy in a room where literally everyone else is laughing and riffing on the joke.

Your humor unit might be defective.

Re: /dev/null is an ACID compliant database

#67

Post by mjb »

Best of all, /dev/null is also serializable (but not strict serializable) under many academic and textbook definitions.

Specifically, these definitions require that transactions appear to execute in some serial order, and place no constraints on that serial order. So the database can issue all reads at time zero, returning empty results, and all writes at the time they happen (because who the hell cares?).

The lesson? Demand real-time guarantees.

Re: /dev/null is an ACID compliant database

#69

Post by brobbin »

charcircuit wrote: post #51
chrisweekly wrote: post #49

Earlier quoted context omitted.

seems you've missed the joke

It's not a funny one if it was one. Of course something is going to be a bad database if it's not a database.

It's nerd humor. You're not supposed to find it funny, but nod along approvingly while noticing how awfully clever you are for noticing the attempt at being funny.
Post reply on HN