KraftyOne

5 ms·

61.
by KraftyOne 11mo ago
> versioning Yes, something like that is needed, we're working on building a good interface for it. > transactional enqueueing But it is safe as long as it's done inside a DBOS workflow. If the connection is lost (process cr
62.
by KraftyOne 11mo ago
The Restate model depends on a long-running external orchestrator to do the "pushing". However, that comes with downsides--you have to operate that orchestrator and its data store in production (and it's a single point of fai
63.
by KraftyOne 11mo ago
Thanks for the great questions! 1. Yes, currently versioning is either automatically derived from a bytecode hash or manually set. The intended upgrade mechanism is blue-green deployments where old workflows drain on old code versions while
64.
by KraftyOne 11mo ago
The main difference is that this is a library you can install and use in any application anywhere, while Durable Functions is (as I understand it) primarily for orchestrating serverless functions in Azure.
65.
by KraftyOne 11mo ago
Haha yes, one thing you can use this for is "long waits" or "long sleeps" where a program waits hours or days or weeks for a notification (potentially through server restarts, etc) then wakes up as soon as the notificati
66.
by KraftyOne 11mo ago
We'll be releasing self-hostable Conductor (the web UI) soon--stay tuned!
67.
by KraftyOne 11mo ago
Fully compatible--see this discussion on Github: https://github.com/dbos-inc/dbos-transact-ts/issues/1115
68.
by KraftyOne 11mo ago
.NET support is something we're considering, but aren't actively building right now.
69.
by KraftyOne 11mo ago
One thing we're looking at right now is what it would take to support Clojure or Kotlin.
70.
by KraftyOne 11mo ago
We actually wrote a blog post recently on why we chose Postgres! https://www.dbos.dev/blog/why-postgres-durable-execution There's no technical reason why this couldn't be done with another database, and we ma
71.
by KraftyOne 11mo ago
Thanks for the great feedback! Yeah, for isolation we recommend each service have its own system database and communicate via clients (so service A starts a workflow in service B by creating a client and calling "client.enqueue").
72.
by KraftyOne 11mo ago
Our primary focus is Postgres. DBOS Python recently added SQLite support, we'll add this to other languages if it proves popular, but no current plans for MySQL. That said, while DBOS requires Postgres for its own checkpoints, it can (
73.
by KraftyOne 11mo ago
There's an observability and workflow management UI: https://docs.dbos.dev/java/tutorials/workflow-management You can view your workflows and queues, search/filter them by any number of criteria, visuali
74.
by KraftyOne 11mo ago
DBOS Python works with gevent out of the box (sync DBOS uses Python threading APIs and psycopg3 that gevent monkeypatches). Have you run into any issues using DBOS Python with gevent? Please let us know!
75.
Show HN: DBOS Java – Postgres-Backed Durable Workflows(github.com)
114 points by KraftyOne 11mo ago|57 comments
76.
Disaggregated Database Management Systems(muratbuffalo.blogspot.com)
2 points by KraftyOne 11mo ago|0 comments
77.
Generalized Consensus: An Alternate Approach to Distributed Durability(multigres.com)
3 points by KraftyOne 1y ago|0 comments
78.
Building Decentralized Workflows That Scale(dbos.dev)
1 points by KraftyOne 1y ago|0 comments
79.
Is Systems Research Just About Making Numbers Bigger?(brooker.co.za)
3 points by KraftyOne 1y ago|1 comments
80.
Temporal-Spatial Locality in Database Design(brooker.co.za)
2 points by KraftyOne 1y ago|0 comments
81.
by KraftyOne 1y ago
DBOS also has a full-fledged workflow visualization and management UI: https://docs.dbos.dev/golang/tutorials/workflow-management
82.
by KraftyOne 1y ago
Yes, there's a full workflow visualization/management interface (not embeddable though): https://docs.dbos.dev/golang/tutorials/workflow-management
83.
by KraftyOne 1y ago
There are DBOS libraries in multiple languages--Python, TS, and Go so far with Java coming soon: https://github.com/dbos-inc No Rust yet, but we'll see!
84.
by KraftyOne 1y ago
We may be a small startup, but we're growing fast with no shortage of production users who love our tech: https://www.dbos.dev/customer-stories
85.
by KraftyOne 1y ago
The durability guarantees are similar--each workflow step is checkpointed, so if a workflow fails, it can recover from the last completed step. The big difference, like that blog post ( https://www.dbos.dev/blog/durable-
86.
by KraftyOne 1y ago
Yes, in any durability framework there's still the possibility that a process crashes mid-step, in which case you have no choice but to restart the step. Where DBOS really shines (vs. Temporal and other workflow systems) is a radically
87.
by KraftyOne 1y ago
Yeah, queue priority is natively supported: https://docs.dbos.dev/golang/tutorials/queue-tutorial#priori...
88.
by KraftyOne 1y ago
1. We also have support for Python and TypeScript with Java coming soon: https://github.com/dbos-inc 2. There are built-in APIs for managing workflow recovery, documented here: https://docs.dbos.dev/producti
89.
by KraftyOne 1y ago
The specific claim is that workflows are started exactly-once in response to an event. This is possible because starting a workflow is a database transaction, so we can guarantee that exactly one workflow is started per (for example) Kafka
90.
Disaggregation: A New Architecture for Cloud Databases(muratbuffalo.blogspot.com)
4 points by KraftyOne 1y ago|0 comments

More ›