Practical Deployment Strategies for Production Python Apps
summary
Describes concrete lessons: a payment front end is built without any database to cut cost, a live site fails under ~10,000 concurrent users, and months are wasted when databases need manual recovery. Recommends AWS Lambda for short jobs to pay seconds instead of 24-hour instances, contrasts DynamoDB convenience with eventual costs of migrating to Postgres for transactions, cites CAP tradeoffs, and shows that automation, monitoring and choosing the right data store actually prevent outages and expensive migrations.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:28Agenda
- 2:58Costs
- 5:43Experience
- 9:03Why
- 9:37Databases
- 11:22Simple Website
- 12:43Database
- 13:39Choosing the right database
- 17:44Integration
related talks
44mPrepping Your Project for Production
50mBest Practices for Python in the Cloud
41mProduction Django: Building a Highly Scalable, Secure Django Site
23mTop tips for developing and deploying on AWS
40mStrategies for Zero Down Time, Frequent Deployments
26mProtoype for Production
34mDeploying Without Crying: Deployment Strategies for Peaceful Nights
30mDeploying scalable Django application on AWS