3 ms·
With redis you're back to the original problem of needing to code things like retries back into your client. Postgres may have some limited abilities to use it
by karmajunkie 9y ago
With redis you're back to the original problem of needing to code things like retries back into your client. Postgres may have some limited abilities to use it as a message queue but you're still going to be missing some of the other features that will end up in faktory like periodic jobs.
If pg works for your situation, that's great, but i don't know why you'd assume that none of these objections have come up before and been responded to.
- manigandham 9y agoIf you want the client-side retry logic too then that requires language-specific libraries, and it seems that's what Faktory requires anyway so this whole thing becomes unnecessary. They couldve just ported the sidekiq library to several languages or use a single C library with language wrappers and gotten the same result with less work.