GraphQL and new limits

[sushruth]

Hi,

I wanted to ask if you would consider, for a Hobby project, using a hybrid limit for functions which could combine the total number of functions per deployment (currently 12) and number of concurrent executions per function (currently 1000).

My main case for this is single endpoint apis like GraphQL. Having a combined limit like total concurrent executions per deployment - 12 * 1000 per current limits, helps such use-cases and keeps it same for others.

Just curious.

[paulogdm]

It is the team's understanding that this limit shouldn't be lifted anytime soon. For backends, Vercel is not a good fit. Using SSR in the platform is also an advanced feature that should be well-thought before doing soon since you can't leverage the edge as you can with SSG/iSSG.

Consider deploying your frontend to Vercel and your backend to another provider, more suited for this type of workload.

[sushruth]

Sounds good. I have a follow up question - what would you suggest the serverless feature of vercel is best suited for?

[mi-na-bot]

We use the SSR pages to provide a rendered view of our advertised inventory for SEO/mobile performance reasons, but host all of the data/APIs in AWS using Lambda w/ API Gateway.

Places, where SEO does not matter like admin portals, are static next.js pages that communicate directly with the AWS backend parts. We use Auth0 directly from the client to get JWTs for authentication, which eliminates another typical SSR thing.