How scalable and performant is Neon, compared to Supabase?
Could you answer these two questions I posted to the Supabase GitHub discussions, but as it pertains to Neon? I am on the fence about which one to go with (Supabase vs. Neon), because I would like a cloud SQL solution which:
1. Is easy to deploy, use, and autoscale, without being a master devops engineer.
2. Allows for a very large (or infinite) amount of db connections (with automatic pooling for fast startup).
3. Returns most queries in under 1 second.
But I'm so far convinced Supabase doesn't fit that bill. But how about Neon? Here are the links to my questions:
https://github.com/orgs/supabase/discussions/32670
https://github.com/orgs/supabase/discussions/32669
GitHub
Realistically, how much concurrent traffic can a Supabase powered s...
ChatGPT provided me with a rough summary table which from reading the Supabase docs, seems pretty accurate: Compute Size Pool Size Max Client Connections Expected Throughput (queries/sec) Small 15 ...
GitHub
Is it possible to have sub-1-second queries using Supabase? · supab...
I am using edge functions for querying the supabase database. Why does it sometimes say (in the edge function logs, where my db calls are made using Kysely) 6s, 8s, 10 seconds even, to do a query! ...
6 Replies
sensitive-blue•11mo ago
Why not just try ?
flat-fuchsia•11mo ago
1) Neon is no-brainer deploy, use, and autoscale. Literally a just clicks.
2) Neon also has a maximum of 10,000 current connections even on its free tier. Note that Neon "sleeps" your database after a few minutes, I think it's 5 minutes by default if no traffic is being sent. The database then needs to be "woken up" again, causing a cold start. In my experience with Neon, cooldown times are typically around 250ms-400ms.
3) I track queries with OpenTelemetry and my stats are 12ms on average, 88ms as max and 1ms as min (no cold starts)
flat-fuchsia•11mo ago
flat-fuchsia•11mo ago
However, I've also worked with Supabase and never had any issues like the ones you mention in the Github discussions. You should try using pg_stat_activity to make sure that Postgres is the problem with the queries. That sounds more like a latency issue than a Supabase issue. Are you sure you chose the region closest to you?
harsh-harlequin•10mo ago
Supabase is 1000% unsafe if you expose your ANON key to the public
You can easily be flooded via Realtime channel or infinite Rest egress using a script that takes 2 seconds to create
I reported the security hole of public Realtime channels being forced on all projects to them months ago, they said there was a PR merging to fix it and.. crickets
Supabase goal is to not provide any protection to consumers of its database so you can get unexpected bills $$$, ignored calls for rate limiting their /rest/ endpoint for years. And then they tell you to use the supabase-js client in your front-end to expose yourself. Sketch company
flat-fuchsia•10mo ago
I have used Supabase multiple times and I can truely tell that it is usable if your use it with their supabase-js client
Beside all you said, their API for storage is easy to spam, their rate limiter is a joke and PostgREST was a mistake. The queries are too limited, spammable and you will also need a view or a custom function to do any real work
Also Idk why they chose Deno for the Edge functions, I think it is now usable but few years ago, it was a nightmare