The latest articles on DEV Community by iyin akinpelumi (@iyin_akinpelumi_2d16539f2). https://dev.to/iyin_akinpelumi_2d16539f2 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3990908%2F5712b5b2-b5a6-47ac-9356-13956690fcab.jpg https://dev.to/iyin_akinpelumi_2d16539f2 en iyin akinpelumi Thu, 18 Jun 2026 12:32:39 +0000 https://dev.to/iyin_akinpelumi_2d16539f2/i-built-an-open-source-f1-api-with-telemetry-race-data-and-driver-history-13a https://dev.to/iyin_akinpelumi_2d16539f2/i-built-an-open-source-f1-api-with-telemetry-race-data-and-driver-history-13a <p>What I Built</p> <p>An open-source Formula 1 REST API powered by FastF1, covering race results, <br> standings, lap analysis, and high-frequency telemetry data from 2018–2026.</p> <p>The Architecture</p> <p>The backend runs on Django + Celery with isolated worker tiers</p> <p>The Interesting Problem</p> <p>Heavy telemetry requests can take 30+ seconds to parse. Instead of making <br> clients poll, I used Redis pub/sub with Server-Sent Events (SSE) so data <br> streams to the client the moment a Celery worker finishes.</p> <p>Try It</p> <p>Docs and API key: <a href="https://f1controlroomdocs.com" rel="noopener noreferrer">https://f1controlroomdocs.com</a></p> <p>Would love feedback from anyone who tries it!</p> api django opensource showdev