Apache Airflow vs NetBox

NetBox 4.7 is the most architecturally significant release in recent memory. Hierarchical models (Region, SiteGroup, Location, DeviceRole, and others) have been migrated from django-mptt to a PostgreSQL ltree column — a change that drops four MPTT columns from every affected table and breaks any plugin using low-level MPTT APIs. On the feature side, cooling infrastructure gets a full first-class data model mirroring the existing power model: CoolingSource, CoolingFeed, CoolingIntake, and CoolingOutflow map the full coolant chain from facility plant to device cold-plate. The 4.6.x line continues parallel maintenance with weekly patch releases.

The ltree migration is a long-overdue structural cleanup — MPTT was a Django-era workaround for hierarchical data that PostgreSQL has handled natively for years. Cooling infrastructure fills the one obvious gap in NetBox's physical infrastructure modeling: power was already end-to-end; cooling wasn't. Together these suggest NetBox is pushing toward completeness as a single source of truth for data center physical plant, not just network topology. Plugin authors will need a meaningful migration effort.

The next major release will focus on stabilizing the plugin ecosystem after the ltree and email system changes. Expect more denormalized caching (the config context pre-render is a template) to reduce per-request query load as NetBox deployments scale.