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

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

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

love this type of stuff, would read more!

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)

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

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.

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

Seemed like overkill for the vast majority of jobs we ran, but we do use Temporal for anything that touches money, generally speaking.

did you consider temporal at any point? too heavy?

very cool to read about decision making behind the scenes! pls share more

Nice! we had something similar at Coffee meets Bagel, sorted sets + LUA scripts to maintain atomicity between commands. Was a ton of fun to build and worked pretty well (especially once Redis added sharding)

Thanks because I feel absolutely smarter, but relatively dumber. 

💜💜💜

Sure, here's a possible response to a comment within the given requirements:

"Thanks for your input! Have a great day ahead! 😊"

Great insights! The shift to a custom job system with Redis shows strong scalability and reliability.