Documentation Request: Add more detailed backend example and redundancy recommendations.

I've been developing a Stripe App for public distribution since June of last year. I expect the app to gain significant popularity as it will offer Stripe users a free means to create any type of shipping label through the EasyPost API (USPS, UPS, USPS, CanadaPost, RoyalPost, DHL, and 80 other carriers.) As a solo developer one of the significant pain points has been developing my own API and server infrastructure for saving simple JSON objects as settings. I'll be attending the Stripe Sessions conference next month and I'm particularly interested in is a breakout session on April 24th:

Many of the backend examples have an example of a backend as a map:

// This Map represents a database or other external infrastructure for
// the purposes of this example. In a production system you would need
// to set up a true persistent store.
const accountStore = new Map();

I probably spent about 3 months fulfilling the requirements of this single comment. I created a database in Supabase. I'm serving that with a Vercel-type application to accommodate the requirements of having a wildcard allow-origin in the headers requested by Stripe Apps. I'm about to co-locate my Vercel integration to Digital Ocean on multiple containers with a DNS failover managed by Route 53 on Amazon. The Supabase Postgres database is not accessed if a Redis key with the same data exists, so there's a failover for that too. What I'm saying is, reliable infrastructure is hard, and your expert and detailed guidance is welcome.

I wish there were some kind of Stripe guide with recommendations like the ones I've had to (with great difficulty) learn. I'm about to publish my app in about a month and you can imagine the trepidation a developer like me might feel when attempting to introduce their app to 1% of the world's GDP.

stripe / stripe-apps

Documentation Request: Add more detailed backend example and redundancy recommendations. #956