3 ms·
As a much more low-level developer, I think they have a point, but not that the interface should be exactly S3. After all, the only thing that's truly "local"
by pjc50 3y ago
As a much more low-level developer, I think they have a point, but not that the interface should be exactly S3.
After all, the only thing that's truly "local" is the processor cache, and on the currently executing core at that. Everything else you have to send out for. Even the DRAM is still ~30ns away. The NVMe devices are on the other end of a "network" defined by the PCIe structure.
So many things on the filesystem would prefer blob semantics of all-or-nothing writes. You don't want to get an updated block in the middle of an executable, image, movie, shared library, etc. But there's no way to expose that differing semantics up to applications.
(not everything! sometimes you do actually want a database! But most of the time you don't want to have to do the required POSIX atomic file update dance)
We know that "everything is a file" was never quite true, but it was a useful principle for POSIX. "Everything is a blob" isn't quite true either, but it may be useful.
> The sort of cloud storage systems described all run on top of POSIX APIs
Is that a benefit or a cost?
- PaulDavisThe1st 3y agoI'm not disputing the idea that sometimes (much) higher level abstractions in an API are a good idea. I'm disputing that the POSIX API is designed to serve anything like the same purpose as (say) S3.