I agree with this. I would be comfortable moving more code to serverless if this weren't as big an issue. I think having a GraphQL server as an API to the datab

I agree with this. I would be comfortable moving more code to serverless if this weren't as big an issue. I think having a GraphQL server as an API to the database may be a good solution, since it can handle a variety of queries/mutations and RPC like behavior. But I still run into this issue a lot whenever I make a new serverless function/project.