/dev/null is an ACID compliant database
1–10 of 203 posts
Re: /dev/null is an ACID compliant database
#2Always 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.
Re: /dev/null is an ACID compliant database
#3[deleted]
Re: /dev/null is an ACID compliant database
#4I'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.
Re: /dev/null is an ACID compliant database
#5Always 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.
It's really fast too.
Re: /dev/null is an ACID compliant database
#6Always 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.
I guess we have a perfect idea for vaporware here. (pun intended)
I am putting my marketing hat on right now.
Re: /dev/null is an ACID compliant database
#7How does a disaster recovery plan with it look like?
Re: /dev/null is an ACID compliant database
#8How does a disaster recovery plan with it look like?
There is never a disaster; reading from /dev/null will return the same result before and after any external event.
Re: /dev/null is an ACID compliant database
#9But is /dev/null web scale?
Re: /dev/null is an ACID compliant database
#10I'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.