The real serverless compute to database connection problem, solved - Vercel
Serverless compute does not mean you need more database connections. The math is the same for serverful and serverless. The real difference is what happens when functions suspend. We solve this issue with Fluid compute.
There is a long-standing myth that serverless compute inherently requires more connections to traditional databases. The real issue is not the number of connections needed during normal operation, but that some serverless platforms can leak connections when functions are suspended. In this post, we show why this belief is incorrect, explain the actual cause of the problem, and provide a straightforward, simple-to-use solution. Link to heading You can stop reading now if Your application uses a modern, stateless protocol like HTTP for database connections (for example, DynamoDB, Fauna, or Fires
saved by
related reading
- Making 768 servers look like 1 — PlanetScaleplanetscale.com
- Mediumfaiqahsan.medium.com
- What is Serverless Architecture? | Datadogdatadoghq.com
- Modal's serverless Servers | Modal Blogmodal.com
- Vercel Functionsvercel.com
- What is Serverless?sst.dev
- How we achieved truly serverless GPUsmodal.com
- Improve database performance with connection pooling - Stack Overflowstackoverflow.blog
- Realtime with serverless using Websocket in AWSunimedia.tech
- Against SQLscattered-thoughts.net
- On-demand Container Loading in AWS Lambdaarxiv.org
- Materialized views are obviously useful – Sophie Alpertsophiebits.com