Debugging Schrodinger's App
summary
A small Flask app with SQLAlchemy simulates cascading failures and actually throws a range of HTTP statuses including 418 I'm a teapot while a lamigo OpenTelemetry tracer auto-instruments the code. The demo is containerized and deployed to ECS, sends messages to SQS, and surfaces distributed traces that link Flask routes to backend services. The local demo behaves intermittently but the ECS deployment records end-to-end traces and highlights 401–403 errors and queue interactions.
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:39Housekeeping
- 3:24Developer advocacy
- 6:09Building applications for scalability and future-proofing
- 7:38Friday night rule
- 11:10Observability rules
- 13:38Local Python debugging
- 15:43Flask to-do errors
- 21:25Cloud-native debugging
- 23:54Distributed tracing
- 25:39OpenTelemetry
- 28:48Python AWS tracing
- 30:55Containerized tracing demo
- 36:36Key takeaways and closing remarks
related talks
27mCoding Competition Software VS Murphy's Law
29mA Trip to the SPA
38mButter smooth, interactive applications with Django...
47mDeprecating Simplicity 3.0
44mDefy Architectural Uncertainty by Building Schrödinger's App
14mTracing: Frontend Issues With Backend Solutions
32mShattering your application into an umbrella project
14mSpeed up fixing app issues using Sentry