I second that. Given the 20,30 or whatever years postgres dealt with all kinds of file systems, hard drive failure codes and what not I would not recommend to jump to any of the newer contenders without a very good reason. I am not biased towards postgres per se but of all the newer components that the digital world can offer I like to be as secure as possible when it comes to the question whether or not my data was actually Written to a disk. It’s a surprisingly hard problem when you have to work with thousands of connections.
> You can classify databases into 4 broad categories based on how they prioritize opposing optimization criteria.
> Flat file
> Relational
> NoSQL
> Blockchain
That's a hellofa classification. It reminds me of the Celestial Emporium of Benevolent Knowledge that "divides all animals into 14 categories: Those that belong to the emperor; Embalmed ones; Those that are trained; Suckling pigs; Mermaids (or Sirens); Fabulous ones; Stray dogs" and so on.
8 comments
[ 3.0 ms ] story [ 27.5 ms ] thread> You can classify databases into 4 broad categories based on how they prioritize opposing optimization criteria.
> Flat file
> Relational
> NoSQL
> Blockchain
That's a hellofa classification. It reminds me of the Celestial Emporium of Benevolent Knowledge that "divides all animals into 14 categories: Those that belong to the emperor; Embalmed ones; Those that are trained; Suckling pigs; Mermaids (or Sirens); Fabulous ones; Stray dogs" and so on.
https://en.wikipedia.org/wiki/Celestial_Emporium_of_Benevole...