GiGStartr-API-concurrency | Stripe Developers | Page 1

rotund ravine Mar 29, 2022, 7:42 PM

#

stoic vine Mar 29, 2022, 7:43 PM

#

I have some asynchronous processes creating API calls - in this case to paymentIntents - as well as some more "bulk" events. AM I correct in believing that in addtition to the rate limits there is no concurrency to an endpoint even if they are explicitly idempotent?

#

(no hurry)

rotund ravine Mar 29, 2022, 7:51 PM

#

Hello 👋
Thanks for your patience 🙂 Still looking into this

stoic vine Mar 29, 2022, 7:56 PM

#

(this is directly observed - you could like starting at event evt_3Kiji3AJ38Y8gLJy1UTeS4q7) _ ...still trying to rmember where to grab the acct

#

acct_1GCV49AJ38Y8gLJy

#

(btw, the events also contradict an answer from yesterday [and a github issue] - the node stripe-js library did retry a 429 API call)

rotund ravine Mar 29, 2022, 8:10 PM

#

So we don't have concurrency per endpoint no, but we do have a rate limit for concurrent requests which applies to all READs and WRITEs respectively

stoic vine Mar 29, 2022, 8:15 PM

#

K. I'm using Firebase Firestore (which has a LOT of concurrency) along with Stripe (which does not), so needed to confirm. I already have event/promise driven concurrency and rate limiters, so easy enough; there's just one point in my Cloud Functions I need to single-thread (well, limit to one instance) to avoid hammering your API. I was pleased to see the 429 error retried, so that's another thing off my plate. Thanks all

rotund ravine Mar 29, 2022, 8:26 PM

#

Thanks for confirming. Apologies, I'm not super familiar with your previous thread but I'll make sure to check it out when I get a chance.

#GiGStartr-API-concurrency