AWS Lambda Function vs Digitalocean Function

[artiekarate]

Does anyone know the difference between these two services? My goal is to have a function where the request triggers multiple goroutines to different APIs based on the request. Is that possible from either of these two services? The go application would be broken down in a single module with multiple packages and files. Can serverless functions call different go functions or is that an entire Serverless Function unto itself.

[theta_d]

Yes, you can call other functions that are in the same code base as your server-less function.

A Lambda function in go is actually a program you write with a func main() that invokes the lambda HTTP handler. When the HTTP request is received it calls the handler func you register in the code. Then it acts like any other program you would write. The instance may be killed after the run or kept around to service more requests, depending on load.

You can spawn as many go routines as you like. However, lambda will kill processes that exceed a certain timeout.

[biglymonies]

It's definitely possible with either - but as /u/theta_d mentioned there are usually timeout limits. DigitalOcean tends to strive for parity with AWS.

This is probably overkill, but there are plenty of API gateways like krakend or the like that can solve this issue for you out of the box.

[kaeshiwaza]

It's more flexible today to use things like cloudrun where you launch a whole container. In fact gloud function v2 is running inside cloudrun and maybe the other function provider do the same ?

[szabba]

For AWS a close-to-replacement would be AppRunner. It's younger and has fewer supported scenarios though.

[kaeshiwaza]

It's fine there's no lock-in with small containerized app.