A place for developers to talk about building on Farcaster.

/dev

A new year's resolution is to write more technical blog posts about challenges we're working on for Warpcast + Farcaster. Here's a post discussing our migration from Faktory to our own hand-rolled job processing framework, and the lessons learned.

A new year's resolution is to write more technical blog posts about challenges we're working on for Warpcast + Farcaster. Here's a post discussing our migration from Faktory to our own hand-rolled job processing framework, and the lessons learned.

https://paragraph.xyz/@sds.eth/building-a-job-processing-system

Did you consider Temporal? Also in OSS land, this is a good one to take inspo from (we're happily using it in production, only dependency is postgres)

Building @warpcast and @farcaster. Previously Coinbase, Brigade, Causes.

Did you consider Temporal? Also in OSS land, this is a good one to take inspo from (we're happily using it in production, only dependency is postgres) https://github.com/oban-bg/oban

enzo's dad 🇬🇷 in LA 🌴 eng @ fanatics.live ⚾️ alexloukissas.com

Oh absolutely. I just shared for potential code reading to take ideas. It’s a really mature project. So it may save you time in the future- maybe!

We use Temporal for a subset of high-value jobs (read: money processing), but it felt like overkill for all jobs, especially at the volume we were doing.

If you really care about what the exact state of a job is and it’s not an inherently idempotent operation that can simply be retried, Temporal seems to be a reliable choice.

Haven’t heard of oban—thanks for putting it on the radar. In our case, it’s really nice to have the job framework also written in TypeScript, since our entire backend codebase is TypeScript.