thanks, that's also what I was not understanding from the article
does that mean you pay for the storage twice (i.e. S3 and Regatta) or is the cache size tunable?
Wouldn't that limit the concurrency of the lambdas to 1? Since they would hold a lock on the db file
How will this deal with workflow versioning? IMO the hardest problem in e.g. Temporal/Cadence
No mention of the resources that are available? The most interesting models currently need beefy GPUs, but I don't think Cloudflare has those...
German here. So few people here have induction because people still think that most pans couldn't be used. But I love it! But also few here use gas. It's mostly ceramic hobs
I would have liked an example of an attack this is supposed to stop. I assume. something like this, but the article really isn't clear about that: You're using a CDN which got compromised, but your CICD servers haven't…
Super nice! It's only missing auto-complete and it'll be light-years ahead of other tools on terms of usability
thanks, that's also what I was not understanding from the article
does that mean you pay for the storage twice (i.e. S3 and Regatta) or is the cache size tunable?
Wouldn't that limit the concurrency of the lambdas to 1? Since they would hold a lock on the db file
How will this deal with workflow versioning? IMO the hardest problem in e.g. Temporal/Cadence
No mention of the resources that are available? The most interesting models currently need beefy GPUs, but I don't think Cloudflare has those...
German here. So few people here have induction because people still think that most pans couldn't be used. But I love it! But also few here use gas. It's mostly ceramic hobs
I would have liked an example of an attack this is supposed to stop. I assume. something like this, but the article really isn't clear about that: You're using a CDN which got compromised, but your CICD servers haven't…
Super nice! It's only missing auto-complete and it'll be light-years ahead of other tools on terms of usability