Content pfp
Content
@
0 reply
0 recast
2 reactions

Varun Srinivasan pfp
Varun Srinivasan
@v
Anyone here worked on an eng team that processed more than 100M background jobs /day? Starting to run into issues with our setup. Looking for ideas on what people typically turn to at this scale.
28 replies
20 recasts
142 reactions

CodinCowboy πŸ– pfp
CodinCowboy πŸ–
@codincowboy
did warpcast end up rearchitecting the stack away from temporal?
1 reply
0 recast
0 reaction

Varun Srinivasan pfp
Varun Srinivasan
@v
we use temporal for processing multi-stage transactions like spending warps. but its way too complicated and expensive for processing generic jobs like "generate a new feed"
1 reply
0 recast
0 reaction

CodinCowboy πŸ– pfp
CodinCowboy πŸ–
@codincowboy
that makes sense where you can replay a stage independently for the complex multi stage processes what did you end up building out for the simple jobs? A simple SQS task queue?
1 reply
0 recast
0 reaction

Varun Srinivasan pfp
Varun Srinivasan
@v
redis + faktory for processing jobs
1 reply
0 recast
0 reaction