Skip to content

docs: add yes/no comparison table for DIY vs Temporal vs AXME #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
George-iam merged 1 commit into from
Mar 25, 2026
Merged

docs: add yes/no comparison table for DIY vs Temporal vs AXME #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,11 +121,14 @@ No polling. No webhooks. No Redis. No glue code. The platform handles retries, t

## How AXME Compares

| Approach | Lines of code | What you operate |
|---|---|---|
| DIY (webhooks + polling + Redis) | ~200 | Everything: retry logic, state machine, timeout jobs, notification service |
| Temporal | ~80 | Temporal server cluster, workers, determinism constraints |
| AXME | 4 | Nothing - managed service with protocol-level guarantees |
| | DIY (webhooks + polling) | Temporal | AXME |
|---|---|---|---|
| Polling | Yes | No | No |
| Webhooks | Yes | No | No |
| Human approvals | Custom build | Possible (heavy) | Built-in (8 task types) |
| Workflow code | Manual state machine | Required (deterministic) | Not required |
| Setup | Low (but fragile) | High (cluster + workers) | None (managed service) |
| Lines of code | ~200 | ~80 | 4 |

---

Expand Down
Loading