Chatbots are deceptive. So much glue code and depending on what you want it to do and how you handle edge cases lots of gotchas. But once you have written one they get easier the next time (no surprise).
Not about the article, but: OpenFaaS' Pricing Page[1] has no pricing on it whatsoever.
You could guess that since the Community edition is MIT licensed that it's free, but then again the language right above it says "non-production or experimental use", where Standard says "production and business use". Now, MIT I know basically means "It's on you, so if you wanna go prod go prod", but that wording just isn't friendly.
Looking over the Community Edition further, I'd honestly be stunned who would ever use this, and thus, what, if anything, about this is "Open":
- Only 5 replicas per function, ie, hope any given function doesn't have more than 5 invocations at once.
- No "scale to zero", (which is the usual cost benefit of serverless)
- There is an in-mem queue, except it's being End-of-Life'd in June, which is... a week from now.
- It does separately support cron triggers! This is great.
- It does not support any other triggers except direct call.
- Can't integrate it with any other K8s deployment tool
I honestly cannot fathom why someone would use this.
6 comments
[ 3.7 ms ] story [ 24.1 ms ] threadYou could guess that since the Community edition is MIT licensed that it's free, but then again the language right above it says "non-production or experimental use", where Standard says "production and business use". Now, MIT I know basically means "It's on you, so if you wanna go prod go prod", but that wording just isn't friendly.
Looking over the Community Edition further, I'd honestly be stunned who would ever use this, and thus, what, if anything, about this is "Open":
- Only 5 replicas per function, ie, hope any given function doesn't have more than 5 invocations at once.
- No "scale to zero", (which is the usual cost benefit of serverless)
- There is an in-mem queue, except it's being End-of-Life'd in June, which is... a week from now.
- It does separately support cron triggers! This is great.
- It does not support any other triggers except direct call.
- Can't integrate it with any other K8s deployment tool
I honestly cannot fathom why someone would use this.
1. https://www.openfaas.com/pricing/
- The queue is in postgres or redis.
- We scale to 0
- We have helm charts for k8s: https://github.com/windmill-labs/windmill-helm-charts
- We support cron and error handlers for cron as functions and we generate a webhook for each functions
- We support local dev and sync from github or deploy directly from our webide
- deployment of a function takes less than 1s
https://github.com/windmill-labs/windmill,