Skip to content

Commit c4ea64e

Browse files
committed
why
1 parent 7950001 commit c4ea64e

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

README.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,16 @@
1111

1212
DBOS provides lightweight durable workflows on top of Postgres. Instead of managing your own workflow orchestrator or task queue system, you can use DBOS to add durable workflows and queues to your program in just a few lines of code.
1313

14-
## Getting started
1514

16-
Install the DBOS Transact package in your program:
15+
## When Should I Use DBOS?
16+
17+
You should consider using DBOS if your application needs to **reliably handle failures**.
18+
For example, you might be building a payments service that must reliably process transactions even if servers crash mid-operation, or a long-running data pipeline that needs to resume seamlessly from checkpoints rather than restart from the beginning when interrupted.
19+
20+
Handling failures is costly and complicated, requiring complex state management and recovery logic as well as heavyweight tools like external orchestration services.
21+
DBOS makes it simpler: annotate your code to checkpoint it in Postgres and automatically recover from any failure.
22+
DBOS also provides powerful Postgres-backed primitives that makes it easier to write and operate reliable code, including durable queues, notifications, scheduling, event processing, and programmatic workflow management.
1723

18-
```shell
19-
github.com/dbos-inc/dbos-transact-go
20-
```
2124

2225
## Features
2326
<details open><summary><strong>💾 Durable Workflows</strong></summary>

0 commit comments

Comments
 (0)