flaviarodriguesf
commented
4 years ago Production Readiness: (see #24 for more info)
- Document how releases are done
- Document how to do a rollback
- Discuss the definition of done (Will we need feature flags?)
- Create billing alarms in Firebase - We might not need this since atm there's no credit card associated with our Firebase account
- Setup DB backup
- Logging/Monitoring
Monitoring tools:
- https://sentry.io/pricing/
- https://rollbar.com/pricing/
- https://www.honeybadger.io/plans/
- https://www.bugsnag.com/pricing
- https://uptimerobot.com/pricing/
- https://newrelic.com/products/browser-monitoring/pricing
- https://www.uptrends.com/pricing
Resources:
- https://jbd.dev/prod-readiness/
- https://medium.com/google-cloud/production-guideline-9d5d10c8f1e
- https://gruntwork.io/devops-checklist/
- http://softwaremanagementblog.net/tag/production-readiness-checklist/
- https://logrocket.com/for/front-end-application-monitoring/
- https://dzone.com/articles/the-top-four-exception-tracking-services
lroyTW
Context: The goal of TW involvement is to deliver something that the organization could use. We are currently trying to work out what stories we need to play before we can advise it’s safe to use our app in production. So far we identified several aspects such as login, securing DB access, HTTPS. Questions: What are the aspects we should not compromise on before declaring our app production-ready? A. Backup should not be compromised, for July delivery we think export script can fulfil the backup requirements too. What would be the right amount of monitoring in our case? Any recommendation on the tools could we use? A. Firebase alerting will need a billing account, need to talk to Charlotte about that. We currently have only one environment. How many would we need in our case? Should we have a separate firebase project per environment? - A. Please refer to #24 Could be interesting: https://docs.honeycomb.io/learning-about-observability/about-instrumentation/client-side-code/
Database backups
Context: It seems that Firebase recommendation is to export the database content as JSON and store it in a bucket. Questions: Should we consider any other backup strategy alternatives? How often should the data be backed up? Are there any standards we should recommend or does it depend on the client? A. Depends on how much HUDS will be used. What slices should be backed up? What happens when someone changes an entry after it was already exported?