But you’re not talking about Postgres or MySQL. You’re talking about a larger bespoke system where one of the components is MySQL. The system you’re describing

But you’re not talking about Postgres or MySQL. You’re talking about a larger bespoke system where one of the components is MySQL. The system you’re describing has: * An object store * A bespoke mechanism for defining schemas * A bespoke mechanism for querying data * A bespoke mechanism for mutating data * A bespoke mechanism for enforcing relationships * A bespoke mechanism for enforcing check constraints The performance bottlenecks I described are not vague at all. They are well known constraints of RDBMS. To come into a discussions about such constraints and say “well if you only use the RDBMS for object storage, and then implement your own bespoke systems to replace all other RDBMS functionality with something completely different, then you don’t need to worry about that” is completely asinine, and to claim that such a system is still an RDBMS is just factually wrong. You might be an excellent distributed system engineer, but it really seems like you don’t actually know what an RDBMS is.