#jj_1325
1 messages · Page 1 of 1 (latest)
Hi @honest folio I found a similar post in stackoverflow here: https://stackoverflow.com/questions/77120578/prevent-save-duplicate-entry-in-our-local-database-during-stripe-webhook/77124230
Yes
Was your question already answered in stack overflow? or you have a follow-up question?
So you have problem in processing events that arrives in a similar time, am I right?
I saw a suggestion to implement a queue system and I agree with it.
Have you tried implementing a queue system?
Not I don't implement queue system.
Now I think implement Kafka system and store all webhook to Kafka and excuate one by one.
But that is not real time if customer have purchased subscription and their succeed request add in last queue so consume some time to excuate and not update immediately
So I avoid queue system
Is store a subscription details like subscription status or start date in our local db. 🤔
If I want to check customer subscription status I think fetch directly from stripe using api. Right???
What stop you from implemtenting a queuing system?
As an example
If 100 user punched subscription so stripe send 100 invoice.payment_succeded webhook now store in queue system and excute that all request one by one.
But it effect on user experience. Not reflecting user subscription immediately
I don't understand why implmenting a queuing system would have impact user experience. Can you tell me your concern?
Queue system like Kafka Right?
First tell me
Is store a subscription details like subscription status or start date in our local db. 🤔
If I want to check customer subscription status I think fetch directly from stripe using api. Right???
Yes you can do that
Generally is the best practices??