Is it right to have a rails model for each background worker type you have? WhatIf the data doesn't need to persist after the job completes?
-
-
Replying to @drewland_2 replies 0 retweets 0 likes
-
Replying to @drewland_
@drewland_@justinxreese@Carols10cents Yeeeeeeeesss?2 replies 0 retweets 0 likes -
Replying to @BillLaboon
@drewland_@justinxreese@Carols10cents I would make a workers subdir1 reply 0 retweets 0 likes -
Replying to @BillLaboon
@BillLaboon@justinxreese@Carols10cents I have 2 workers. One that processes incoming texts and one that sends texts.1 reply 0 retweets 0 likes -
Replying to @drewland_
@BillLaboon@justinxreese@Carols10cents it seems like I putting the objects directly in redis seems wrong1 reply 0 retweets 0 likes -
Replying to @drewland_
@BillLaboon@justinxreese@Carols10cents so my solution we to create a table for each and just pass the Id into reque/redis1 reply 0 retweets 0 likes
@drewland_ @BillLaboon yeah don't put the objects in redis. Sidekiq has good docs on these concepts in its wiki
-
-
Replying to @Carols10cents
@Carols10cents@drewland_ I misunderstood question AND forgot how redis works (used diff @ TDC). Removing myself from Twitter for a while.0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.