So these guys have a storage system on top of Amazon S3 with a distributed (timestamp based) RW mutex locking, that uses NTP (github.com/beevik/ntp). That seems

So these guys have a storage system on top of Amazon S3 with a distributed (timestamp based) RW mutex locking, that uses NTP (github.com/beevik/ntp). That seems to be about it. https://github.com/minio/minio/blob/master/pkg/bucket/object/lock/lock.go https://github.com/minio/minio/blob/master/pkg/bucket/object... https://github.com/minio/minio/blob/master/pkg/dsync/drwmutex.go https://github.com/minio/minio/blob/master/pkg/dsync/drwmute... And this is their test: https://github.com/minio/minio/blob/master/pkg/dsync/dsync_test.go https://github.com/minio/minio/blob/master/pkg/dsync/dsync_t... I just browsed quickly but it is littered with Amazon Simple Storage Service hardcoded bits like this: https://github.com/minio/minio/blob/master/pkg/bucket/object/lock/lock.go#L96 https://github.com/minio/minio/blob/master/pkg/bucket/object... There is not a single document that I can find that discusses the MinIO architecture. I guess "MinIO is a simple wrapper around S3 with a homegrown distributed state tech using NTP and it is 'fast!'" does not make for a sexy doc. The column "trouble with OSS distributed DBs" without Jepsen tests has probably already been written. There should also be one about "competitor's mature product bashing blogs are HN clickbait".