[unlocksmith]

Minio is designed to work in conjunction with Kubernetes and Mesos like external orchestrators. GlusterFS, Ceph and Swift has builtin orchestration. So when you measure Minio's scalability, you should measure Kubernetes instead.

Multi-tenant cloud-native architecture requires each tenant to be intentionally kept small (limited by the failure domain). This way, when you scale from few hundred tenants to millions, your complexity doesn't scale proportionately. Million'th instance of Minio is as simple as its first instance. If you are looking for a global namespace, simply use ngnix like proxy load-balancers in the front. Orchestration tools are well understood at scale unlike Ceph and Swift.

Building monolithic distributed systems has a number of challenges. They do not scale beyond a point. Failure may take down the entire site. Troubleshooting is hard. No CI/CD. Entire system has to be upgraded at once with planned downtime. Security breach exposes the whole system..

-ab Architect (Minio and formerly GlusterFS)