From CSV to APIs: When to Stick with File Exchange and When to Migrate.
summary
Airline data flow moves from cron-generated CSVs in S3 buckets to on-demand REST APIs that validate schema, emit HTTP status codes and enable monitoring. CSVs cause schema fragility that once produces 3 days outage and file-name changes that cause 2 days delays; credentials in shared buckets leak control. The team builds a REST API, runs CSV and API in parallel for a rollout window, and reports faster availability, fewer critical failures, and clearer observability.
AI-written summary · about
chapters (6)
- 0:00CSV vs API integration
- 1:27CSV as the right choice
- 6:22Migrate to APIs
- 11:02CSV integration case study
- 19:21CSV vs API use cases
- 21:30Key takeaways
related talks
28mBetter APIs through Better More Timely Data
26mData with a mission: a COVID-19 API case study
43m40 Minutes to Build Serverless REST and GraphQL APIs
52mDesigning and Implementing REST APIs For the Long Haul
23mModernise file transfers with APIs
25mCloud Databases, ELT, and APIs – A Perfect Storm
26mAPI archaeology: guiding the API journey
16mAPI Integration with JS: Scalable, and Future-Ready Systems