From notebook to production using
summary
Code converts a notebook into a Flask API, a React frontend and a live Heroku deployment, with the notebook refactored into domain models, repository interfaces and tests. A slow kernel density / nearest‑neighbor approach gets replaced by a compiled Hungarian algorithm implementation, cutting memory from ~20–30MB to about 5–10MB. Data lives in s3 or local pickle repos, results serialize to JSON, search scores return frame ids and the prototype UI and API both work end to end.
AI-written summary · about
chapters (16)
- 0:00Notebook to production
- 2:57Video analysis problem
- 8:03Domain models from notebook
- 12:23Hungarian algorithm optimization
- 16:51Unit tests for matcher
- 20:04App and infrastructure layers
- 26:23Tracking data visualization
- 31:07Flask API for search
- 35:30React frontend visualization
- 40:17Heroku deployment
- 46:45Cloppy library intro
- 51:28Open source resources
- 52:09Q&A memory optimization
- 53:56Q&A response time scaling
- 56:11Q&A frame filtering
- 58:00Q&A open source contributions
related talks
27mNotebook To Production
34mNotebooker: Production and Scheduling for your Jupyter Notebooks
20mFrom notebooks to production - bringing devops to scientists
49mUntitled13.ipynb
40mPython and pandas as back end to real-time data driven applications
01h 23mImproving Your Data Modeling Work Through Open-Source Software
38mJumping into Jupyter Notebooks
44mUsing Python with Hadoop to create production ready big data applications
