CyberHuginn

Home

/

Notes

/

building-django-healthkit

Building django-healthkit

How a simple health endpoint for Bidar turned into django-healthkit, a lightweight Django health-check package.

Django

Backend

Packages

DevOps

Aug 9, 2026 · 2 min read

Building django-healthkit

While building Bidar, I needed a simple health endpoint for the projects that Bidar was going to monitor.

At first, it was nothing fancy.

Just a 200 OK response with a small JSON payload:

{
  "status": "ok"
}

Then I added the application version.

But I started thinking: what if this endpoint actually told me whether the application was healthy?

That question turned a tiny endpoint into a small side project.

I started building django-healthkit — a simple Django package for checking the health of an application.

The first version is intentionally small. It currently checks the most important infrastructure dependencies I need:

  • Database connectivity
  • Redis connectivity

The plan is to gradually add more checks, such as:

  • CPU usage
  • Memory usage
  • Disk usage
  • More infrastructure and application-level checks

The goal isn't to build another huge monitoring system.

I want django-healthkit to stay simple, lightweight, and useful — something I can plug into Bidar, but also something that could be useful on its own for Django applications or even as a basic health check endpoint for environments like Kubernetes.

What started as a simple:

GET /health/

is slowly becoming a small piece of infrastructure.

And honestly, that's one of the things I like about building software:

sometimes a tiny problem turns into a useful tool.

You can find the package on PyPI.

Related Notes

The API Worked. The Architecture Didn’t.

A practical look at why a working API does not always mean a healthy architecture, covering coupling, synchronous work, database bottlenecks, caching, microservices, failure modes, and the importance of clear boundaries.

When Redis Is Not the Solution

Redis is fast and extremely useful, but that doesn't make it the right solution for every backend problem. A practical look at when Redis helps with caching, rate limiting, OTPs, locks, queues, sessions, and temporary data—and when it simply adds unnecessary infrastructure and complexity.

Django Transactions: What atomic() Actually Protects

Learn how Django transactions work, what transaction.atomic() actually protects, and how to handle race conditions, row locking, database constraints, nested transactions, and post-commit side effects with select_for_update() and on_commit().

The Hidden Cost of Django REST Framework Serializers

Learn how Django REST Framework serializers can cause N+1 queries, slow API responses, and unnecessary database work—and how to optimize them with select_related, prefetch_related, annotations, and better serializer design.

Building a Django Package — Part 4: Publishing django-healthkit to PyPI

In this final part, we prepare django-healthkit for release, build and validate the package, test it on TestPyPI, publish it to PyPI, and create a Git tag and GitHub release.

Building a Django Package — Part 3: Health Check Manager and Endpoint

In Part 3, we connect the database and cache health checks, build the health check manager, expose a Django health endpoint, measure check latency, and return a structured health status.

Building a Django Package — Part 2: Database and Cache Health Checks

In this part, we implement the first health checks for django-healthkit, covering database connectivity and Django cache functionality with simple, independent, and testable checks.

Building a Django Package — Part 1: Setting Up django-healthkit

In this part, we build the initial structure of django-healthkit, configure the package with pyproject.toml, and prepare it for development.

Building a Secure Webhook Receiver for Server-to-Server Communication

How I built a secure FastAPI webhook receiver using RSA signatures to enable authenticated server-to-server communication, proxy requests, and connect applications across different network environments.

Why I Switched to Conventional Git Commit Messages

Why I switched from inconsistent Git commit messages to a Conventional Commits style, with practical examples for cleaner and more maintainable Git history.

Designing a Gold Jewelry E-Commerce Database with Django

Learn how to design a scalable Django database for a gold jewelry e-commerce platform by modeling products, attributes, and purchasable product variants using real-world domain-driven design principles.

How to Fix Common Next.js 16 Build Errors (Proxy, Dynamic Rendering & Revalidation)

Learn how to fix common Next.js 16 build errors, understand Proxy, Dynamic Rendering, and Revalidation, and improve your application's SEO and performance.

Why I Built cyber-ui: A Minimal Design System for Developers

How my projects, from backend systems to monitoring tools, led me to create a minimal and personal UI foundation.

End of note.