Major Domo Database - PostgreSQL database service for SBA bot
Users were seeing stale roster data on the website even after updates because browsers cached responses for 30 minutes. Direct API calls showed correct data, confirming this was a client-side caching issue. Changes: - Remove @add_cache_headers decorators from all player endpoints - Keep @cache_result (Redis server-side caching) for performance - Server cache still gets invalidated on write operations Benefits: - Users always see fresh data (within Redis TTL of 30 minutes max) - Server cache invalidation now effective for end users - Minimal performance impact (~10ms Redis lookup vs 0ms browser cache) - Redis already provides 80-90% of caching benefit Trade-off: - Browsers now make request to server on every page load - Server handles more requests but Redis makes them fast - For fantasy sports, fresh data > marginal performance gain Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| app | ||
| migrations | ||
| scripts | ||
| test-storage | ||
| tests | ||
| .dockerignore | ||
| .env | ||
| .gitignore | ||
| =2.9.0 | ||
| CLAUDE.md | ||
| data_consistency_check.py | ||
| DATA_CONSISTENCY_REPORT.md | ||
| db_engine.py | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Dockerfile.optimized | ||
| LICENSE | ||
| main.py | ||
| migrations.py | ||
| pd_master.db | ||
| pytest.ini | ||
| REFACTOR_DOCUMENTATION.md | ||
| requirements.txt | ||
| VERSION | ||