I've been shipping serverless ever since it was launched on AWS. More recently I am using Google. The biggest thing I am struggling with right now is how to ap

I've been shipping serverless ever since it was launched on AWS. More recently I am using Google. The biggest thing I am struggling with right now is how to appropriately split projects for module size. This may be more of an issue with Firebase functions than AWS because it's a lot easier to create separate projects with AWS for firebase and constrain the project. Google Firebase Functions very much assumes a big package architecture. We could break it up into multiple firebase projects but that separation creates a lot of annoyances. It'd be awesome if you could split packages up so the resources don't have to be shared within the various functions. tl;dr want to split modules and functions up with explicit dependencies to optimize bundle size / cold boot. Additionally I found it to be an anti-pattern to use any DB that requires a connection pool vs HTTP based commands. It's annoying as heck to manage connection pools with serverless and seems downright buggy or broken. If you want to support it you need to centralize it with something like PGpool which seems like a big anti-pattern. I hate dynamodb but am loving Google's offering (firebase firestore or datastore).