KraftyOne

8 ms·

91.
Show HN: Postgres-Backed Durable Workflows in Go(github.com)
5 points by KraftyOne 1y ago|1 comments
92.
Redesigning Data Systems to Be Agent-First(muratbuffalo.blogspot.com)
8 points by KraftyOne 1y ago|1 comments
93.
How to Learn About Systems(notes.eatonphil.com)
4 points by KraftyOne 1y ago|0 comments
94.
The Evolution of Logical Replication in PostgreSQL(enterprisedb.com)
2 points by KraftyOne 1y ago|0 comments
95.
by KraftyOne 1y ago
Kafka is great for streaming use cases, but the big advantage of Postgres-backed queues is that they can integrate with durable workflows, providing durability guarantees for larger programs. For example, a workflow can enqueue many tasks,
96.
by KraftyOne 1y ago
Observability is a big advantage, another advantage (in the context of DBOS specifically) is integration with durable workflows, so you can write a large workflow that enqueues and manages many smaller tasks.
97.
Lessons from Testing Distributed Systems(dbos.dev)
2 points by KraftyOne 1y ago|0 comments
98.
Dynamo, DynamoDB, and Aurora DSQL(brooker.co.za)
1 points by KraftyOne 1y ago|0 comments
99.
by KraftyOne 1y ago
That's interesting, I'll take a look! I had always thought of it as an Azure-only thing.
100.
by KraftyOne 1y ago
Like Inngest and Restate, DBOS provides durable workflows. The difference is that DBOS is implemented as a Postgres-backed library you can "npm install" into your project (no external dependencies except Postgres), while Inngest a
101.
by KraftyOne 1y ago
Yeah, I think in that case you should have auto-scaling DBOS workers all pulling from a queue and a FastAPI backend using the DBOS client to submit jobs to the queue. Queue docs: https://docs.dbos.dev/python/tutorials&#
102.
by KraftyOne 1y ago
I'd love to learn more about what you're building--just reach out at peter.kraft@dbos.dev. One option is that you have DBOS workflows that schedule and submit jobs to an external worker app. Another option is that your workers use
103.
by KraftyOne 1y ago
Would love to learn more about what you're building--what problems or parts of your system would you solve with Dagster vs DBOS?
104.
by KraftyOne 1y ago
We wanted to make workflows more lightweight--we're building a Postgres-backed library you can add to your existing application instead of an external orchestrator that requires you to rearchitect your system around it. This post goes
105.
by KraftyOne 1y ago
Both do durable workflows with similar guarantees. The big difference is that DBOS is an open-source library you can add to your existing code and run anywhere, whereas Durable Functions is a cloud offering for orchestrating serverless func
106.
by KraftyOne 1y ago
As the post says, the exactly-once guarantee is ONLY for steps performing database operations. For those, you actually can get an exactly-once guarantee by running the database operations in the same Postgres transaction as your durable che
107.
Build durable workflows with Postgres(dbos.dev)
161 points by KraftyOne 1y ago|56 comments
108.
The Cost of Being Wrong(jack-vanlightly.com)
3 points by KraftyOne 1y ago|0 comments
109.
Lessons from scaling PostgreSQL queues to 100k events per second(rudderstack.com)
5 points by KraftyOne 1y ago|0 comments
110.
How to Test Durable Execution(dbos.dev)
2 points by KraftyOne 1y ago|0 comments
111.
Benchmarking Durable Workflow Architectures(dbos.dev)
3 points by KraftyOne 1y ago|0 comments
112.
Handling Failures with Forks(dbos.dev)
2 points by KraftyOne 1y ago|0 comments
113.
CRDTs: Pros and Cons (Lattices and Lettuces?)(jhellerstein.github.io)
6 points by KraftyOne 1y ago|0 comments
114.
Why Your Workflows Should Be Postgres Rows(dbos.dev)
3 points by KraftyOne 1y ago|0 comments
115.
Show HN: DBOS Python 1.0 – Lightweight Durable Workflows Built on Postgres(github.com)
6 points by KraftyOne 1y ago|0 comments
116.
Benchmarking Architectural Tradeoffs in Durable Workflows(dbos.dev)
2 points by KraftyOne 1y ago|0 comments
117.
Jeeps, Ferraris, and Other Engineers(maheshba.bitbucket.io)
1 points by KraftyOne 1y ago|0 comments
118.
Why Your Workflows Should Be Postgres Rows(dbos.dev)
5 points by KraftyOne 1y ago|0 comments
119.
Monarch: Google's Planet-Scale In-Memory Time Series Database [pdf] (2020)(vldb.org)
4 points by KraftyOne 1y ago|0 comments
120.
Torn Write Detection and Protection(transactional.blog)
3 points by KraftyOne 1y ago|0 comments

More ›