4 ms·
Function URLs aren’t part of lambda, they’re just a thin abstraction around API Gateway v2 (http APIs) that allow all calls, and have randomly generated domains
by lukevp 3y ago
Function URLs aren’t part of lambda, they’re just a thin abstraction around API Gateway v2 (http APIs) that allow all calls, and have randomly generated domains, so you’re not gaining anything and losing some functionality by doing this instead of running an API GW with lambda proxy integration yourself. If setting up API GW is too difficult, you could use SAM or Serverless Framework to automatically provision it. Then you can have a real domain, SSL, failover, endpoint validation, etc.
- arrakeenrevived 3y ago>so you’re not gaining anything and losing some functionality by doing this instead of running an API GW You're gaining the fact that Function URLs are free while APIGW can be pretty costly, as well as the fact that Function URLs are fantastically less complex than APIGW if your use cases fit it.
- tlarkworthy 3y agoFunction URLs are not limited to 30 seconds. That's massive
- maerF0x0 3y agoI think they are only an asynchronous invocation in that case though? The reason they do that is they dont want your connections holding a port for 15 minutes.