qianli_cs

7 ms·

1.
Postgres Select Distinct Does Not Scale(dbos.dev)
4 points by qianli_cs 5d ago|0 comments
2.
PostgreSQL system catalog changes across versions(richyen.com)
1 points by qianli_cs 19d ago|0 comments
3.
Fifty Years of Transaction Processing Research(arxiv.org)
3 points by qianli_cs 4mo ago|0 comments
4.
We ditched database triggers for audit logs(pydantic.dev)
2 points by qianli_cs 4mo ago|0 comments
5.
by qianli_cs 8mo ago
That's fair, the idea itself isn't new. Workflows/durable execution have been around forever (same story in Elixir). The differences are in the implementation and DX: the programming abstraction, how easy recovery/debugg
6.
by qianli_cs 8mo ago
Thanks for sharing, interesting project! One thing that stood out to me is that some fairly core features are gated behind a Pro tier. For context, there are prior projects in this space that implement similar ideas fully in OSS, especially
7.
The success of 'natural language programming'(brooker.co.za)
4 points by qianli_cs 9mo ago|0 comments
8.
by qianli_cs 10mo ago
This post seems to be published in a hurry. Under "How it works" section a bunch of duplication, and I think they should make the blog post exactly once :) Excerpt from the blog post: > During replay, your code runs from the be
9.
by qianli_cs 10mo ago
I really enjoyed this post and love seeing more lightweight approaches! The deep dive on tradeoffs between different durable-execution approaches was great. For me, the most interesting part is that Persistasaurus (cool name btw) use of byt
10.
by qianli_cs 10mo ago
Yeah, in the long term, we're supporting more languages. But we aren't actively building new languages right now.
11.
by qianli_cs 10mo ago
To build on what Peter said, we need to stay focused and make one backend solid before expanding. But architecturally, nothing prevents us from supporting more engines going forward.
12.
by qianli_cs 11mo ago
I'm excited about this because durable workflows are really important for making AI applications production ready :) Disclaimer: I'm working on DBOS, a durable workflow library built on Postgres, which looks complementary to this.
13.
Finding my rhythm again(jeremydaly.com)
67 points by qianli_cs 11mo ago|6 comments
14.
by qianli_cs 11mo ago
We're seeing issues with multiple AWS services https://health.aws.amazon.com/health/status
15.
Sanitized SQL(ardentperf.com)
4 points by qianli_cs 11mo ago|0 comments
16.
Barbarians at the Gate: How AI Is Upending Systems Research(arxiv.org)
8 points by qianli_cs 11mo ago|0 comments
17.
Supabase raises $100M at $5B valuation as vibe coding soars(fortune.com)
3 points by qianli_cs 1y ago|0 comments
18.
by qianli_cs 1y ago
In DBOS, workflows can be invoked directly as normal function calls or enqueued. Direct calls don't require any polling. For queued workflows, each process runs a lightweight polling thread that checks for new work using `SELECT ... FO
19.
by qianli_cs 1y ago
Good questions! DBOS naturally scales to distributed environments, with many processes/servers per application and many applications running together. The key idea is to use the database concurrency control to coordinate multiple proce
20.
by qianli_cs 1y ago
I think one potential concern with "checkpoint execution state at every interaction with the outside world" is the size of the checkpoints. Allowing users to control the granularity by explicitly specifying the scope of each step
21.
by qianli_cs 1y ago
I think a clearer way to think about this is "at least once" message delivery plus idempotent workflow execution is effectively exactly-once event processing. The DBOS workflow execution itself is idempotent (assume each step is i
22.
by qianli_cs 1y ago
That password is only used by the GHA to start a local Postgres Docker container ( https://github.com/dbos-inc/dbos-transact-golang/blob/main/c... ), which is not accessible from outside.
23.
The Next Horizon of System Intelligence(sigops.org)
2 points by qianli_cs 1y ago|0 comments
24.
by qianli_cs 1y ago
I think it was likely caused by the cache trying to compare the tag with Docker Hub: https://docs.docker.com/docker-hub/image-library/mirror/#wha... > "When a pull is attempted with a tag, the Registr
25.
Pydantic AI Durable Execution(ai.pydantic.dev)
4 points by qianli_cs 1y ago|0 comments
26.
by qianli_cs 1y ago
The main advantage is the same architectural benefit DBOS provides in other languages: you only need to deploy your application, so there's no separate coordinator to run. All functionality (checkpointing, durable queues, notification&
27.
by qianli_cs 1y ago
Those are great questions! For versioning, we recommend keeping each version running until all workflows on that version are done. It's similar to a blue-green deployment: each process is tagged with one version, and all workflows in i
28.
by qianli_cs 1y ago
Thanks for sharing your insights! You nailed the key tradeoffs of most durable workflow systems. The callback-style programming model is exactly the pain point we aim to solve with DBOS. Instead of forcing you into a custom async runtime, D
29.
by qianli_cs 1y ago
I've been building an integration [1] with Pydantic AI and the experience has been great. Questions usually get answered within a few hours, and the team is super responsive and supportive for external contributors. The public API is e
30.
Dynamo, DynamoDB, and Aurora DSQL(brooker.co.za)
5 points by qianli_cs 1y ago|0 comments

More ›