user
16 days ago
16 days ago
16 days ago
Hello HN!
I built Django Orbit because I needed a better way to debug Django applications. While Django Debug Toolbar is great, its DOM injection approach causes issues with modern frontend stacks (HTMX, React, Vue) and JSON APIs.
Orbit takes a different approach: "Satellite Observability". It runs on its own isolated URL (/orbit/) and records everything happening in your app without interfering with your frontend.
It records: - HTTP Requests & Responses - SQL Queries (with N+1 detection) - Background Jobs (Celery, RQ, Django-Q) - Exceptions & Logs - Cache operations (Redis, Memcached) - And newly added in v0.6: Database Transactions & File Storage monitoring
It's drop-in: `pip install django-orbit` + middleware. Zero config needed to start.
Tech stack: Django + HTMX + Tailwind (lightweight, no build step).
Repo: https://github.com/astro-stack/django-orbit
Docs: https://astro-stack.github.io/django-orbit/
Web: https://labs.wearehik.com Would love your feedback!
15 days ago
I like the satellite concept for avoiding frontend conflicts. My main concern would be the database load. Since you are storing data via standard migrations, does that mean every Celery task writes to the primary Postgres instance? I suspect that would become a bottleneck pretty quickly with high-throughput queues, or at least cause significant write amplification on the main db.