I doubt he remembers me. In any case even back then he would say that the database should just do everything in our staff meetings.
Many of us were smirking back then each time it came up, but it looks like now, 20 years later, he is finally having a go at it!
He is one of the smartest people I have ever met - as far as I can tell :) So if there's someone who can do it, it is him and the team he assembles.
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
await ctxt.invoke(Shop).
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..?
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 limits: https://docs.temporal.io/cloud/limits#throughput , and allows self-hosting.
How does DBOS compare to its competitors?
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.
We got it, it's awesome, stop making NEW THREADS where everyone who wasn't in the first 500 of these submissions posts the same things
It seems to take the durable workflow idea and lock you into a specific language, operating system, and database, when other projects in the same space give you choice over those components.
1. It's a serverless platform. It manages application deployments, providing a simpler experience than trying to bolt a durable execution framework onto an app deployed on Kubernetes.
2. Transactional guarantees. DBOS does durable execution in the same transactions as your business logic, so it guarantees exactly-once execution for most operations while other workflow solutions are at-least-once. More details here: https://docs.dbos.dev/explanations/how-workflows-work
3. Database time travel, which greatly enhances observability/debugging/recovery. More details here: https://docs.dbos.dev/cloud-tutorials/timetravel-debugging
I can run linux on a raspberry pi. I can run kubernetes on a raspberry pi (if I wanted to). Can I run DBOS on a raspberry pi?
My first thought was this, https://en.wikipedia.org/wiki/OpenSSI
Never an especially viable option, but one that always fascinated me.
This tech feels like fancy RDBMS triggers backed (and made unique) by a distributed log. Looks very much like the same tech as Flink's statefun and Restate.dev.
Just like SSD gave us LSM trees and RocksDB, it seems like this is the higher level abstraction that Kafka enables. It's going to be interesting to see how it pans out.
DBOS will definitely be an interesting thing to watch out for, if it looks to make things available at a low level.
Web page says "So Matei and I launched a joint MIT-Stanford open-source R&D project to prototype DBOS"
and it points to this site: https://dbos-project.github.io/ and https://github.com/DBOS-project
Neither contain much source code at all.
Under pricing on the main page it says:
Can I run DBOS Cloud on-premises?
The DBOS SDK can deploy your transactional, fault-tolerant TypeScript code locally (any platform) for testing purposes. For production deployment, deploy your code from the SDK to DBOS Cloud
But that is for DBOSCloud, but I guess it goes for DBOS as well?