Just ideally the dev experience should be `result = await somethingThatMayHaveBe... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		johtso on March 10, 2023 \| parent \| context \| favorite \| on: Launch HN: Defer (YC W23) – Zero-infrastructure ba... Just ideally the dev experience should be `result = await somethingThatMayHaveBeenCalledBefore(id=txnref, params)` You shouldn't need to first do a check to see if the task already exists using a different api, and then choose whether or not to run a new task. At least this is my preference.. a-la Durable Objects. If you don't specify a custom unique id when calling the task it would then be treated as a task that can (and would make sense to be) run multiple times (i.e. not idempotent).

gearnode on March 10, 2023 [–]

Completely agree with you on the importance of idempotency. We will release our implementation shortly with a pattern close to the following:

``` const somethingThatMayHaveBeenCalledBefore = idempotent(myFunc, txnref); const result = await somethingThatMayHaveBeenCalledBefore(params); ```

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact