kopper @w.on-t.work · 10/08/2026like i cant see any real reason for monolithic "User Service" classes. theres no reason not to split every individual action into its own service at which point all you have are a bunch of classes with a single function because you can't DI easily otherwise 100
kopper @w.on-t.work · 10/08/2026and like all DI "services" end up building on top of a few basic resources like a database connection pool which, like, how many times do you even set those more than once. why not globals? 100
kopper @w.on-t.work · 10/08/2026hm, something like sqlite multi-db partitioning could be a valid reason to have multiple scoped database connections... so i guess two distinct lifetimes of "services": global variables and asynclocals 100