Developer, you will respect your prod!
summary
The talk explains how to prepare, monitor and maintain a production application using logging, monitoring and metrics best practices. It follows a case study of “HamsterGram” (an Instagram‑like app for hamster photos) and describes what the team did or avoided, the operational preparations, and the practices that keep the service healthy in production.
AI-written summary · about
chapters (38)
- 0:00Speaker introductions
- 1:00Why this conference?
- 1:55Amsterdam introduction
- 2:50The team
- 3:42Speed vs. rushing
- 4:56Documentation before coding
- 5:40Let the horses loose
- 5:52Writing tests
- 6:50Running tests
- 7:38Advantages of automation
- 8:58Automating delivery
- 11:21The database
- 14:26The real production deployment
- 16:02Production deployment
- 16:42The real go-live
- 17:01We’re happy!
- 17:23Once the app is in production
- 17:33We’ll change our work organization
- 18:29Reproducing a production bug with mocked data
- 19:40Can we have an ISO production environment?
- 21:00Can we have bugs in production?
- 21:45Should we implement automated processes?
- 22:23How to manage incidents?
- 23:13How to improve incidents?
- 24:31Application versions
- 26:04Adapting your organization
- 27:00Improving your production
- 27:29Logs
- 29:02Frontend logs
- 29:55Metrics
- 31:11Observability
- 32:30Automating delivery
- 34:26Tests
- 35:30Relevant logs
- 36:00Respect your production
- 36:36Others are done
- 37:10The hamsters
- 37:31Questions
related talks
30mA Well-Maintained Production Application
21mMonitoring Your Apps is not About Devops
43mGetting Your System into Production and keeping It There
38mMillions of Apps: What we've Learned
53mProject life in production: operational tips
34mMonitoring for devs. The necessity or self-indulgence
38mPractical Guide to Application Observability in 10 Steps
50mYou build it, you run it (why developers should also be on call)