zlacker

One of my favourite spaces and presentation in readme is clear and immediately told me what it is and most of the key information that I usually complain is missing.

However I am still missing a section on why this is different than any of the other existing and more mature solutions. What led you to develop this over existing options and what different tradeoffs did you make? Extra points if you can concisely tell me what you do badly that your 'competitors' do well because I don't believe there is a one best solution in this space, it is all tradeoffs

>>sixhob+(OP)
Sorry I am dumb and commented after clicking on the link. I would just add your hn text to the readme as that is exactly what I was looking for

>>sixhob+p
Done [1]. We'll expand this section over time. There are also definite tradeoffs to our architecture - spoke to someone wanting the equivalent 1.5m PutRecord/s in Kinesis, which we're definitely not ready for because we're persist every event + task execution in Postgres.

[1] https://github.com/hatchet-dev/hatchet/blob/main/README.md#h...