> Pricing you cannot predict. Every operation is metered. One runaway alarm loop billed a pre-launch developer $34,000 in eight days, with no users and no warning.
It's amazing that we still lack the ability to set a hard cost cap on a lot of cloud services/API, as the consumer you usually have a rough idea of what something is going to cost (I say rough because pricing out AWS is always fun) and an idea of what the lower bound "oh shit that isn't right" limit should be, so why can we not set that.
You shouldn't be getting an unexpected $34K bill (unless it's within variance and you are running a very large system).
Cynically the opaqueness of this stuff has to be by design/intention at this point.
The criticism of Cloudflare here is reasonable, I think. I really like the CF building blocks - they're neat and conceptually useful and quite unusual. I think they could have a better developer experience though (though it probably is better than when I last tried it), and I also think they could have a little more confidence in their overall platform's usefulness and open up more of their model as open source. For example, I'd love to run my CF workers in CI locally without creating infrastructure (again, this may have changed since I last tried it).
I don't know if it is ai generated or at the opposite hand written a little bit fast but I find this article very hard to read despite the concepts in it being simple.
celld and workerd give you Durable Objects if you run another daemon. This is a library your app loads, with state stored in the SQL database you already have (Postgres, MySQL and SQLite supported). No daemon required, no new infrastructure and monitoring, no broker, and no vendor account.
Pre-1.0, MIT, TypeScript, in browser (with WASM SQLite), and Ruby too. Happy to answer anything.
This looms nice and I starred but you just want actors and there are other options for that you might want to compare, I like rika actors, or temporal (not actors exactly but durable state and workflows). This is a space where a few very similar technologies after looked from different lenses sell themselves widely differently. So if you know what you want and the names of the things you are searching for you can get a thing that looks 90% like te rest, sorry a bit rambly. But yeah it would be nice to add some comparisons against these technologies as well.
> Pricing you cannot predict. Every operation is metered. One runaway alarm loop billed a pre-launch developer $34,000 in eight days, with no users and no warning.
It's amazing that we still lack the ability to set a hard cost cap on a lot of cloud services/API, as the consumer you usually have a rough idea of what something is going to cost (I say rough because pricing out AWS is always fun) and an idea of what the lower bound "oh shit that isn't right" limit should be, so why can we not set that.
You shouldn't be getting an unexpected $34K bill (unless it's within variance and you are running a very large system).
Cynically the opaqueness of this stuff has to be by design/intention at this point.
The criticism of Cloudflare here is reasonable, I think. I really like the CF building blocks - they're neat and conceptually useful and quite unusual. I think they could have a better developer experience though (though it probably is better than when I last tried it), and I also think they could have a little more confidence in their overall platform's usefulness and open up more of their model as open source. For example, I'd love to run my CF workers in CI locally without creating infrastructure (again, this may have changed since I last tried it).
Why chose the Solid- line of naming, considering that's the rails provided naming. I makes it look like this is official.
I don't know if it is ai generated or at the opposite hand written a little bit fast but I find this article very hard to read despite the concepts in it being simple.
I couldn't parse "Getting that model has meant taking on something else."
The article is 1000% ai slop
Author here.
celld and workerd give you Durable Objects if you run another daemon. This is a library your app loads, with state stored in the SQL database you already have (Postgres, MySQL and SQLite supported). No daemon required, no new infrastructure and monitoring, no broker, and no vendor account.
Pre-1.0, MIT, TypeScript, in browser (with WASM SQLite), and Ruby too. Happy to answer anything.
This looms nice and I starred but you just want actors and there are other options for that you might want to compare, I like rika actors, or temporal (not actors exactly but durable state and workflows). This is a space where a few very similar technologies after looked from different lenses sell themselves widely differently. So if you know what you want and the names of the things you are searching for you can get a thing that looks 90% like te rest, sorry a bit rambly. But yeah it would be nice to add some comparisons against these technologies as well.