Growing Your Cloud Application
summary
Dashboards alone don’t detect real problems; set alerts early and install the Google Cloud mobile app so new errors hit phones. Prioritize robust end-to-end tests over brittle unit suites (Cypress/Protractor work but break often). Capture client-side errors with Firebase Crashlytics and session replay tools like LogRocket, and avoid PII by using SSO. Enforce least-privilege IAM, automate backups and test recoverability, and use feature flags/canary releases or small third‑party services (stats glitch, phaser) instead of extra custom code.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:39a. Automate monitoring, but in the right way
- 8:09b. Automate testing, but in the right way
- 12:55a. Busy isn't always the same as productive
- 17:49a. Provide a way for users to send feedback with friction
- 20:44b. Track all user actions
- 32:11a. Have backups instead of good intentions
- 34:44b. Code is a liability
- 36:14c. Feature flags and canary deployments
related talks
34m7 Missing Factors for Your Production-Quality 12-Factor Apps
42mThriving in the cloud: Going beyond the 12 factors
18mArchitecting Resilient Cloud Native Applications: A Practical Guide to Deployment and Runtime
50mJourneys To Cloud Native Architecture: Sun, Sea & Emergencies
47mManaging Application Events in the Cloud
36mApps Need Data
53mAppSec & Microservices
25mGoogle Core Web Vitals–Mobilising and Testing Front-End Performance in Microservices