I mostly agree with the commenter you’re replying to - but I think you bring up a good point. Once you start disconnecting tables from one another, and end up w

I mostly agree with the commenter you’re replying to - but I think you bring up a good point. Once you start disconnecting tables from one another, and end up with lots of small data stores, does it still make sense to bother with the Postgres at all? I think that its value as a layer becomes unclear. Sure its battle-tested and has great query planning and similar tools, but those base based on assumptions that are largely violated with the re-architecture. I think the architectural decoupling benefits mentioned are basically already proven though. I’ve worked at places that had many NoSQL tables per team, each logically distinct, and at places that had one database with 50+ tables in it. The breakup can be nice, in the same way that “serverless” is nice - data storage becomes entirely abstracted to the developer.