4 ms·
Yeah you raise totally valid points here. The current thinking is that the $5 tier would end up having a small set of "fair use" restrictions on it for things
by llamaLord 4y ago
Yeah you raise totally valid points here.
The current thinking is that the $5 tier would end up having a small set of "fair use" restrictions on it for things like max request payload, max workflow execution time, etc. Payload size is the big one, I'm less worried about execution time as the underlying engine that executes the logic is all Async & non-blocking so it's pretty efficient.
I want to have a very clear line though between the allowances that are restricted to encourage a higher price-point (workflows, node's, executions), vs the one's that are there to ensure things don't explode.
The benchmark goal would be for raw compute to equate to <10% of total revenue, which I'm confident is very achievable with some sensible restrictions that still allow 99.9% of use-cases.
At this early stage, I'd probably say that anyone who's processing 1M requests with 33kb bodies each prooobably isn't my initial target customer haha.
- tmikaeld 4y agoI don't doubt that you'll be able to cover it on the large whole, since only a fraction of users would parse JSON bodies that large, however, those heavy users will probably use a large portion of the resources. It's hard to weigh conversion numbers vs heavy usage, a low price like this will certainly help adopt new users and in large numbers. It might even make it worth tolerating the (few) heavy users. Or you put it in cloudflare workers, which can parse 1.5MB of JSON within 50ms CPU-time and call it a day (10M requests/5$).