await ctxt.invoke(Shop).
is repeated 5 times in what I'd say are about 7 active lines of code. Then, because it's so unreadable, you have a comment per line that needs to explain what the line does. Hmm..DBOS Operating System
21–30 of 30 posts
Re: DBOS Operating System
#22Re: DBOS Operating System
#23DBOS will definitely be an interesting thing to watch out for, if it looks to make things available at a low level.
Re: DBOS Operating System
#24This really doesn't look as cool as it sounds. The title / header reminds one of operating systems of the past; attempts to have the OS as database like OS/400, but the reality seems far more like a cloud hosted Linux + Postgres + Node/TS + Temporal (or something like it). As in, nothing to see here that we didn't already trivially have. Is there more to see besides the rock star at the helm?
Re: DBOS Operating System
#25Re: DBOS Operating System
#26Go to the About page -> all engineers.
If everything's running on top of a database -> how well does any of this scale? What is it going to cost me to run at scale?
In the durable execution space, flawless.dev has no pricing, but they're clear that they're still in alpha; temporal.io does have clear pricing for their hosted model: https://temporal.io/pricing/ , clearly documents limits: https://docs.temporal.io/cloud/limits#throughput , and allows self-hosting.
How does DBOS compare to its competitors?
Re: DBOS Operating System
#27Go to the Pricing page -> no pricing. Go to the About page -> all engineers. If everything's running on top of a database -> how well does any of this scale? What is it going to cost me to run at scale? In the durable execution space, flawless.dev has no pricing, but they're clear that they're still in alpha; temporal.io does have clear pricing for their hosted model: https://temporal.io/pricing/ , clearly documents…
I did a lot of research and product evaluations, was always honest about my intent and how much decision power I had. It worked out maybe once - most companies insisted on wasting time of multiple people just to ... Waste even more time and not give even unofficial rought estimate, or basic definitions from license. It kind of matters if it's paid for "every employee" or "every employee that uses the software". Apparently just for me.
Re: DBOS Operating System
#28This really doesn't look as cool as it sounds. The title / header reminds one of operating systems of the past; attempts to have the OS as database like OS/400, but the reality seems far more like a cloud hosted Linux + Postgres + Node/TS + Temporal (or something like it). As in, nothing to see here that we didn't already trivially have. Is there more to see besides the rock star at the helm?
We provide strong guarantees (like exactly-once transactions) and new features (like database time-travel, you can replay any production trace in a local dev environment). We also believe there's a lot of value in the ease-of-use and simplicity that comes from our architecture: it takes only a few minutes to deploy an app to the cloud.
Check out this 3-minute video for a quick overview of what we offer: https://www.youtube.com/watch?v=O6fau5TVmdA
Re: DBOS Operating System
#29Yikes...the gobbledygook that passes for a code-example on the home page is not exactly an advertisement. await ctxt.invoke(Shop). is repeated 5 times in what I'd say are about 7 active lines of code. Then, because it's so unreadable, you have a comment per line that needs to explain what the line does. Hmm..
The code examples indeed demonstrate exactly the sort of confusion that the entire product screeches.
Just seems like a way to rope people into a service (DBOS Cloud) they don't actually need (which may or may not be expensive, as information regarding this service is greatly lacking.)
Perhaps it's true that this is a project in the early stages, but with the heavy-handed sales language baked into the site, perhaps it was announced a bit too early..?
Re: DBOS Operating System
#30Yikes...the gobbledygook that passes for a code-example on the home page is not exactly an advertisement. await ctxt.invoke(Shop). is repeated 5 times in what I'd say are about 7 active lines of code. Then, because it's so unreadable, you have a comment per line that needs to explain what the line does. Hmm..
Anyone who took the time to actually check this out can see that it's just TS over postgres with muddled logic and arbitrary features that seem to try to solve problems that only vaguely exist. The code examples indeed demonstrate exactly the sort of confusion that the entire product screeches. Just seems like a way to rope people into a service (DBOS Cloud) they don't actually need (which may or may not be expensive…