A Django REST interface over public SpaceX mission data: cumulative launch, landing and reflight statistics, upcoming and past launches with mission detail, and live Dragon capsule tracking. It is an independent project with no affiliation to SpaceX.
Four groups, each its own Django app with its own serializers, exceptions and health check: statistics, upcoming launches, past launches, and Dragon tracking. The root endpoint is a directory — it names every other endpoint with an absolute URL and a description, so the API is discoverable without opening documentation first.
When the service needs to shed load, the data routes are not disabled inside each view — they are never registered. A single availability flag decides whether the app URL patterns are appended at all, so an unavailable deployment answers 404 for them rather than running a view that immediately gives up.
The root directory endpoint stays mounted either way, which means a caller can always reach something that explains the state. The alternative, a flag checked at the top of every view, is the same behaviour spread across a dozen places and forgotten in the thirteenth.