@bananas Basically, you can split up the complexity of an application into many smaller parts by using packages, right? And then reuse those packages across projects, whenever you need the same functionality.

But the glaring issue always ends up being that this doesn't work for anything that deals with persistent state; because database structure is defined on an application level, a library can't make assumptions about it, and if it does, it can very easily conflict with something else in destructive ways.

What I'm looking for is something that allows modularization of persistently stateful systems too - for example, a "user management" library that implements login/registration/session/etc. functionality *and* internally manages the storage of user data, while still allowing you to reference "a user" from, say, an application-specific "threads" table/collection, and have that reference be stable and basically work how you'd expect from a system with relational integrity.