I talked to the Cloudflare team at Clerk's ecosystem hackathon last year, showed them Inngest, and they were really enthusiastic about our model. They said something like "we've been thinking about this for some time but couldn't figure it out".
APIs are only part of it. "Flow control" — concurrency, waitForEvent, sleeps, batching, debounce, etc is key. Observability is key. People emulating our APIs is always going to happen, and it's no big deal. The only sad part is that they don't call out any inspiration; we literally asked them to work with us for this with R2 last year.
It's always good to get validation, and I'm glad our API makes sense to folks. The feedback we get from developers is always extremely good.
I talked to the Cloudflare team at Clerk's ecosystem hackathon last year, showed them Inngest, and they were really enthusiastic about our model. They said something like "we've been thinking about this for some time but couldn't figure it out".
APIs are only part of it. "Flow control" — concurrency, waitForEvent, sleeps, batching, debounce, etc is key. Observability is key. People emulating our APIs is always going to happen, and it's no big deal. The only sad part is that they don't call out any inspiration; we literally asked them to work with us for this with R2 last year.
It's always good to get validation, and I'm glad our API makes sense to folks. The feedback we get from developers is always extremely good.
Disclaimer: I'm a founder of Inngest.