As for the idea itself, I believe there IS a recipe for doing this right: - Role Based Access Permissions (RBAC) for course-grained control over database objec

As for the idea itself, I believe there IS a recipe for doing this right: - Role Based Access Permissions (RBAC) for course-grained control over database objects (tables, procedures, etc.) - Row Level Security (RLS) for fine-grained control over data items (e.g. multinenant) For correctness: - custom data types - custom domains - check constraints - triggers - procedures For loose coupling: - views - procedures For QoS: - quotas (timeouts, row limits, data limits) That gets you most of the way there. You would still want a connection pooler and a rate limiter, of course, outside the DB.