Staging

Due to privacy restrictions and testing requirements a staging environment is needed for the implementation of Bright Kit.

The database associated with this environment should be a sub-set of anonymized data sourced from production to ensure testing results are accurate. Recent data with timestamps from "today" are required to test all experiences inside of the app views. We suggest creating a script to update the sub-set of data daily, or updating just the timestamps. Alternatively you can create a read-replica of your production database that updates at least every 7 minutes. Modern cloud based read-replicas can propagate changes almost instantly.

This environment's infrastructure and setup should be as close as possible to your target production environment. Staging will be used for testing both your Bright Kit implementation and end-user app interactions.

📘

No load testing or PEN tests are required to be performed prior to going live

This environment can be utilizing a small resource set to keep costs low but should not scale down to 0 resources or 0 availability. Set your scaling to at minimum of at least 1 to avoid testing timeouts.

🚧

Do not remove/disable this environment after project completion as new features and bug fixes depend on your test data for validation.

Production

We suggest enabling dynamic scaling for your production to avoid issues with high utilization during mass messaging of Users.