How do serverless functions work
Unanswered
Abyssinian posted this in #help-forum
AbyssinianOP
I'm trying to learn about next.js with vercel but atm I'm a bit confused as to when a serverless function is used. Assuming the free plan, is absolutely everything running on the server running as a serverless function (and so anything taking longer than 10s will error?). I'm basically a bit confused as to how backend code is handled and what the limits are. I'm also a bit confused as to why vercel is considered ideal for static websites in particular if you can still run dynamic websites with javascript?
12 Replies
@Abyssinian I'm trying to learn about next.js with vercel but atm I'm a bit confused as to when a serverless function is used. Assuming the free plan, is absolutely everything running on the server running as a serverless function (and so anything taking longer than 10s will error?). I'm basically a bit confused as to how backend code is handled and what the limits are. I'm also a bit confused as to why vercel is considered ideal for static websites in particular if you can still run dynamic websites with javascript?
In summary,
- User sends a request to serverless function
- a instance spins up, which'll process the request and returns the response
- It'll have a timeout and it'll throw a error if it doesn't return a response
- You're billed for the time the instance spends processing the request
- The instance returns a response, and the instance remains idle for I think 5 mins
- instance will shut down if it doesn't receive a request in that time
- User sends a request to serverless function
- a instance spins up, which'll process the request and returns the response
- It'll have a timeout and it'll throw a error if it doesn't return a response
- You're billed for the time the instance spends processing the request
- The instance returns a response, and the instance remains idle for I think 5 mins
- instance will shut down if it doesn't receive a request in that time
You can check from here also:https://vercel.com/docs/fundamentals/what-is-compute
@Anay-208 | Ping in replies In summary,
- User sends a request to serverless function
- a instance spins up, which'll process the request and returns the response
- It'll have a timeout and it'll throw a error if it doesn't return a response
- You're billed for the time the instance spends processing the request
- The instance returns a response, and the instance remains idle for I think 5 mins
- instance will shut down if it doesn't receive a request in that time
*this is just a summary, and some points might be missing/little inaccurate
@Anay-208 | Ping in replies In summary,
- User sends a request to serverless function
- a instance spins up, which'll process the request and returns the response
- It'll have a timeout and it'll throw a error if it doesn't return a response
- You're billed for the time the instance spends processing the request
- The instance returns a response, and the instance remains idle for I think 5 mins
- instance will shut down if it doesn't receive a request in that time
AbyssinianOP
Under what circumstances are serverless functions needed. Does absolutely any backend logic require a serverless function? If so, wouldn't even page routing be done as a serverless function?
It is used as it is scalable
@Anay-208 | Ping in replies Using serverless functions is a choice
AbyssinianOP
I see. If I want to, for example, connect to a database somewhere else and query it and do some logic on it before returning it back to the user, I don't need to use a serverless function in that case?
@Abyssinian I see. If I want to, for example, connect to a database somewhere else and query it and do some logic on it before returning it back to the user, I don't need to use a serverless function in that case?
As mentioned it is a choice.
I personally use serverless function for connecting to postgreSQL and querying.
I personally use serverless function for connecting to postgreSQL and querying.
@Anay-208 | Ping in replies As mentioned it is a choice.
I personally use serverless function for connecting to postgreSQL and querying.
AbyssinianOP
What's the benefit of it if it has tight restrictions such as only allowing 10s of operations? What's preventing me from running all the logic on the server that's currently hosting the website?
Is it just the fact that the logic can be overwhelming to that one server and serverless functions auto distribute that execution onto multiple servers as needed based on demand (i.e. The scalability you mentioned).?
Is it just the fact that the logic can be overwhelming to that one server and serverless functions auto distribute that execution onto multiple servers as needed based on demand (i.e. The scalability you mentioned).?
@Abyssinian What's the benefit of it if it has tight restrictions such as only allowing 10s of operations? What's preventing me from running all the logic on the server that's currently hosting the website?
Is it just the fact that the logic can be overwhelming to that one server and serverless functions auto distribute that execution onto multiple servers as needed based on demand (i.e. The scalability you mentioned).?
For a website, it shouldn't take more than 10s to respond.
Additionally, you can increase the limit if you're on vercel Pro plan.
Additionally, you can increase the limit if you're on vercel Pro plan.
@Anay-208 | Ping in replies For a website, it shouldn't take more than 10s to respond.
Additionally, you can increase the limit if you're on vercel Pro plan.
AbyssinianOP
I see but is my understanding of its benefits correct there?
You can read more about it in vercel documentation, where its explained in detail