AHAObjectWorld: Grundidee (2023)

This was my first try to capture the concept and idea of resolving the separation of "metadata and payload" (aka "meta + data") on the filesystem level.

It describes in an overview how this would instantly (positively) affect file/data handling - and resolve many existing "issues/challenges" that come with the current "files-in-folders and metadata stored somewhere else" paradigms.

Therefore it's in German, because it was intended as "braindump note" to exchange these ideas and concepts with a good friend of mine.

I am assuming that "Object Storage" is able to save any kind of key/value data as-is generically.

At the time of this recording, I have never used or setup an Object Storage before. However, more than 1 year later, the concept still stands very well.

The following remarks may be added:

a) "S3-compatible" systems are (IMO) currently unsuitable for awesome meta+data handling as described here, due to arbitrary limitations of metadata/tagging length and encoding.

b) Object Storage systems designed and implemented before Amazon S3 are more likely to support this properly.
Something like [OpenStack Swift](https://ubuntu.com/openstack), etc.
ANSI T10 Object Base Storage Standard may also be a good reference:
https://ieeexplore.ieee.org/document/...

b) No need to go "object storage" for providing the core features that come with meta+data on the filesystem level: Extended File Attributes (or similar filesystem features) are very likely sufficient.
See: https://en.wikipedia.org/wiki/Extende...