Hacker News Reader

Comment by sickcodebruh | Hacker News Reader

Supabase looks so good and keeps getting better. I started playing with it a couple months ago and could see myself loving it. One of my biggest problems right now is inertia: I’m comfortable with my existing tools (RDS, S3, lambda) and thinking about building a new product while also adding new tools is a tough pill to swallow. But the product sure makes a strong case!

Resumable uploads is a big deal for what I’m working on. But I’m also blocked by another issue, maybe a Supabase engineer on the thread can weight in. I’m using ffmpeg on AWS lambda to transcode media files after successful upload to S3. Lambda makes it easy to add ffmpeg binaries via lambda layers. Supabase functions don’t seem to provide any such option. Is there a way to solve this within Supabase as it exists now?

I’m also curious about function timeouts. If I have a file conversion that takes a couple minutes, is a Supabase function the right way to go?

View on HN

> Is there a way to solve this within Supabase as it exists now?

No, not right now. However we do have a planned path to this. The 3 features we will release are:

1. Custom execution limits/timeouts for Edge Functions.

2. WASM support in Edge Functions

3. Storage Webhooks, which can trigger an Edge Functions

Features 1 & 2 will be possible with the Edge Runtime we released yesterday[0]. Feature 3 is already possible using our Postgres Database Webhooks[1], and we will also provide additional support for this directly in the storage server

[0] Edge Runtime discussion: https://news.ycombinator.com/item?id=35525222

[1] Postgres Database Webhooks: https://supabase.com/docs/guides/database/webhooks

I was trying to do the same thing (ffmpeg to do file transformations on upload) and couldn't figure it out with Supabase functions. After poking around in the Deno discord for awhile, it seems that ffmpeg.wasm for Deno just isn't much of a thing yet. I was able to get it working with Vercel functions, but it was a total nightmare and the runtime made it a non-starter. I landed where you started: just do it in Lambda!

This was almost exactly my trajectory. It’s a shame cause Supabase is so close to being a slam dunk for me but this complicates it. Are you using S3 for storage or were you able to stick with Supabase and use upload complete callbacks to trigger the lambda?

that's great feedback. Our Functions team has seen this - we'll see what we can do

Thank you! This was one of the two major blockers for me, the other being lack of presigned upload URLs and I see that landed with this release!

That is the same inertia we see while selling to early stage company.

I also see quite some people build out in supabase and migrate to AWS, especially if they want SOC2 or some compliance certifications. The Compliance automation tools work really well with known cloud providers.

Just as a note, Supabase received SOC2 Type 2 compliance last week (we've had Type 1 for a long time already) and now we're working on HIPAA.

Reply on news.ycombinator.com