mirror/hatchet
1
0
Fork 0
mirror of https://github.com/hatchet-dev/hatchet.git synced 2026-02-21 07:49:48 -06:00
Code Issues Packages Projects Releases Wiki Activity

Update postgres-events-table.mdx

Browse Source
This commit is contained in:
abelanger5
2024-11-20 12:10:40 -05:00
committed by GitHub
parent 980649e673
commit 2d54fa0dd1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
frontend/docs/pages/blog/postgres-events-table.mdx
View File

@@ -29,7 +29,7 @@ For those who would like to dive deeper into code or view full query examples th
## What's the use-case?
There are lots of reasons to store events in your system — in this post, I'd like to focus on the three common use-cases that we've recently seen while building Hatchet:
There are lots of reasons to store events in your system — in this post, I'd like to focus on the three common use-cases that we've recently seen while building [Hatchet](https://hatchet.run):
- [Exposing state transitions to users](#state-transitions) - used in our system to provide a timeline of events for a task.
- [Aggregates](#aggregate-data) - used for tracking the percentage of succeeded/failed tasks over time.