#jamesfroud-billing-laravel
1 messages · Page 1 of 1 (latest)
oh boy that;'s a loooot of words 😅
Since you have thousands of products, I'd have it cached in your own database
pulling it from our API will be slow since https://stripe.com/docs/api/products/list and https://stripe.com/docs/api/prices/list return 100 objects at most per page
So yeah my advice is to have all products and prices in your database, sync them in Stripe to map your product/price to the prod_123 and price_123 in Stripe but use your own database as the source of truth
Does that make sense?
Hi, yeah that makes sense, it was what I was thinking as didn't think Stripe would appreciate lots of API calls. I guess the key would be to make sure that the prices in our database and in Stripe are always in sync as well, have a queue worker running listening for any updates on our database and update Stripe and never let anyone update a product/price in Stripe directly.