#kelly_best-practices

1 messages ยท Page 1 of 1 (latest)

fallow saffronBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1254910654683287612

๐Ÿ“ Have more to share? Add details, code, screenshots, videos, etc. below.

errant ore
#

Hi there!

#

Best practices are not to test in production ๐Ÿ˜…

surreal otter
#

Fair enough, we use the test cards in stage.

errant ore
#

Testing in test mode should reflect how things will work in live mode, and monitoring live mode for real activity after going live is our recommendation.

surreal otter
#

But we have observed slightly different behavior in prod, e.g. more delays, different event ordering, etc

#

Gotcha, thanks ๐Ÿ‘

errant ore
#

re: event ordering, events are not guaranteed to be delivered in a specific order

#

re: delays, do you have more context? I suspect you're seeing longer request/response times since communication with card networks is happening in live mode (and only simulated in test mode)

surreal otter
#

Thanks, we'll focus on observability for now.

#

Yes, exactly

#

No issue on stripe's end

#

just that we wanted to test our system with potential variances that only happen in production