Shared February 10, 2019
Most network file systems are either a layer over an existing filesystem (NFS, CIFS), or are develped from scratch to have separate, replicated, purpose-designed databases for metadata and object store (GFS, Glusterfs). At the same time, most database engines provide (or can be coerced into providing) replication and all the ACID properties needed for a high-performance filesystem.
Idea: Use a database engine (Postgres, MariaDB) on raw partitions with a fast separate nVME log file; build POSIX file system semantics on top. It's pretty obvious that this could work; I'm just starting to implement it so performance and durability can be measured.
linux.conf.au is a conference about the Linux operating system, and all aspects of the thriving ecosystem of Free and Open Source Software that has grown up around it. Run since 1999, in a different Australian or New Zealand city each year, by a team of local volunteers, LCA invites more than 500 people to learn from the people who shape the future of Open Source. For more information on the conference see https://linux.conf.au/
#linux.conf.au #linux #foss #opensource
The Tragedy of systemd
Explaining File Systems: NTFS, exFAT, FAT32, ext4 & More
Quantum computing explained with a deck of cards | Dario Gil, IBM Research
Tutorial: Building the Simplest Possible Linux System - Rob Landley, se-instruments.com
Edward Snowden: How Your Cell Phone Spies on You
But Mummy I don't want to use CUDA - Open source GPU compute
NYLUG Presents: Lennart Poettering -on- Systemd in 2018
6 Mistakes New Linux Users Make
Macs are SLOWER than PCs. Here’s why.
A case study in incrementing a language's major version: PHP
The mind behind Linux | Linus Torvalds
My year on the front line - cleaning infected sites
The kernel report
Writing Viruses for Fun, not Profit
Learning the Linux File System
Firmware security, why it matters and how you can have it
Why Isn't Functional Programming the Norm? – Richard Feldman