Wait for a Requirement Before Adding a Queue

0:00Payment If you said this you get a 5 out of 10 Can you

0:03even tell why this one isn't optimal This answer makes absolutely no sense unless

0:07you're processing like millions and millions of records Depending on how you design your

0:13payment system you can easily just get away with letting Stripe retry Like what

0:18is the actual value in standing up a new simple queue service and then

0:23retrying the events on your own infrastructure Articulate to me what is the actual

0:27value in doing that There is none

0:30Unless again you're processing a ton of different records Whether or not you build

0:34dedicated infrastructure to retry the message or you just flip on a config on

0:39the Stripe side to retry the message the message is going to get retried

0:44regardless The only way this makes sense is if you have a ton of

0:48different events or you have a specific requirement on how often these messages need

0:53to be retried Don't over engineer