serverless
storage
serverless | storage | |
---|---|---|
2 | 2 | |
295 | 466 | |
13.6% | 4.7% | |
8.6 | 9.3 | |
7 days ago | 2 days ago | |
TypeScript | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
serverless
-
HTTP vs. WebSockets: Which one is the fastest for Postgres queries at the Edg
Here is the actual package used [1]. I thought it would have been similar to serverless-pg[2] with initiation outside the handler as with the node implementation. Any insights into how they achieve connection caching (similar to pooling?) on the edge?
[1]: https://github.com/neondatabase/serverless
- Storage on Vercel
storage
-
Direct Postgres connection to Supabase from Vercel Edge in Next.js
Is anyone aware of a way to make a direct connection to Postgres with transaction support on Vercel Edge functions? The 'pg' package doesn't work on edge for me. The obvious answer would be @vercel/postgres but I find their lack of documentation rough and for whatever reason I can't get it to connect on my local computer using the Supabase-provided local database connection string. This is apparently a known issue (https://github.com/vercel/storage/issues/123, https://github.com/vercel/examples/issues/701) where in order to make this (or neon's package) work you need a WebSocket proxy? Is a direct Postgres connection from edge just impossible right now? Or do others have it working somehow?
-
Introducing Vercel Postgres, KV, and Blob
I tried tried the vercel kv client to see if I could use it inside of this little shimming code, but first I couldn't get the types to work, and then second looking at the types further its just the @upstash/redis client with a couple extra functions that is API based, which is fair, but, I'm already using redis.
What are some alternatives?
wsproxy
lagon - Deploy Serverless Functions at the Edge. Current status: Alpha
neon-vercel-zapatos - Example use of Neon serverless driver on Vercel Edge Functions with Zapatos
kv-connect-kit - Minimal Typescript client implementing the KV Connect protocol. Access Deno KV remotely from any Javascript environment like Node, Cloudflare Workers, Bun, Deno, and the browser.
serverless-pg - A package for managing PostgreSQL connections at SERVERLESS scale
supabase - The open source Firebase alternative.
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
serverless-next.js - ⚡ Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components [Moved to: https://github.com/serverless-nextjs/serverless-next.js]
cloudflare-for-speed-and-security - Scale faster and save big with the global edge cloud platform - https://kerkour.com/cloudflare-for-speed-and-security
serverless-next.js - ⚡ Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components
relay-starter-kit - 💥 Monorepo template (seed project) pre-configured with GraphQL API, PostgreSQL, React, and Joy UI. [Moved to: https://github.com/kriasoft/graphql-starter-kit]
node-starter-kit - Node.js / GraphQL project template pre-configured with TypeScript, PostgreSQL, login flow, transactional emails, unit tests, CI/CD workflow.