5 ms·

Very interesting concept, however it's a bit soured by the fact that Container-based FaaS is never mentioned, and it removes a decent chunk of the negatives aro

by sofixa 3y ago

Very interesting concept, however it's a bit soured by the fact that Container-based FaaS is never mentioned, and it removes a decent chunk of the negatives around FaaS. Yeah you still need to deal with the communication layer (probably with managed services such as SQS or Pub/Sub), but there's no proprietary runtime needed, no rewrites needed between local/remote runtime environments.

willsmith72 3y ago
what are some examples of container-based faas? like you put your docker image onto lambda?
- sofixa 3y ago
  * Google Cloud Run - https://cloud.google.com/run/docs/deploying#command-line https://cloud.google.com/run/docs/deploying#command-line * OpenFaaS - https://www.openfaas.com/blog/porting-existing-containers-to-openfaas/ https://www.openfaas.com/blog/porting-existing-containers-to... * AWS Lambda - https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/deploy-lambda-functions-with-container-images.html https://docs.aws.amazon.com/prescriptive-guidance/latest/pat... * Scaleway Serverless Containers - https://www.scaleway.com/en/serverless-containers/ https://www.scaleway.com/en/serverless-containers/ * Azure Container Instances - https://learn.microsoft.com/en-us/azure/container-instances/container-instances-overview https://learn.microsoft.com/en-us/azure/container-instances/... Probably others too, those are just the ones I know off the top of my head. I see very little reason to use traditional Function-based FaaS, which forces you into a special, locked-in framework, instead of using containers that work everywhere.
  - willsmith72 3y ago
    ok yeah so like an image on lambda, totally agree, a lot of the pros of serverless without a lot of the cons
- dprotaso 3y ago
  https://knative.dev/ https://knative.dev/ - (CloudRun API is based on this OSS project)
chrismccord 3y ago
Bring-your-own-container is certainly better than proprietary js runtimes, but as you said it carries every other negative I talk about in the post. You get to run your language of choice, but you're still doing all the nonsense. And you need to reach for the mound of proprietary services to actually ship features. This doesn't move the needle for me, but I would be happy to have it if forced to use FaaS.

by sofixa 3y ago

willsmith72 3y ago

what are some examples of container-based faas? like you put your docker image onto lambda?

sofixa 3y ago
* Google Cloud Run - https://cloud.google.com/run/docs/deploying#command-line https://cloud.google.com/run/docs/deploying#command-line * OpenFaaS - https://www.openfaas.com/blog/porting-existing-containers-to-openfaas/ https://www.openfaas.com/blog/porting-existing-containers-to... * AWS Lambda - https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/deploy-lambda-functions-with-container-images.html https://docs.aws.amazon.com/prescriptive-guidance/latest/pat... * Scaleway Serverless Containers - https://www.scaleway.com/en/serverless-containers/ https://www.scaleway.com/en/serverless-containers/ * Azure Container Instances - https://learn.microsoft.com/en-us/azure/container-instances/container-instances-overview https://learn.microsoft.com/en-us/azure/container-instances/... Probably others too, those are just the ones I know off the top of my head. I see very little reason to use traditional Function-based FaaS, which forces you into a special, locked-in framework, instead of using containers that work everywhere.
- willsmith72 3y ago
  ok yeah so like an image on lambda, totally agree, a lot of the pros of serverless without a lot of the cons
dprotaso 3y ago
https://knative.dev/ https://knative.dev/ - (CloudRun API is based on this OSS project)

chrismccord 3y ago

Bring-your-own-container is certainly better than proprietary js runtimes, but as you said it carries every other negative I talk about in the post. You get to run your language of choice, but you're still doing all the nonsense. And you need to reach for the mound of proprietary services to actually ship features. This doesn't move the needle for me, but I would be happy to have it if forced to use FaaS.