Most tenants run more than one environment side by side – development, staging, production. From now on, they all keep making progress, even when one of them is busy.

For a long time, Enterspeed has enforced fairness between tenants, so no single tenant can monopolise processing and hold up everyone else on the platform. We've now brought that same principle between environments within a single tenant.

Previously, jobs ran through a single first-in, first-out queue for the whole tenant. So a large backlog in one environment sat in front of everything else, and jobs from other environments had to wait their turn behind it. Now Enterspeed picks jobs from every environment that has work waiting. If development queues a large batch – a bulk import, a full re-processing, a schema experiment – production jobs added afterwards no longer sit behind that entire backlog. Each environment keeps flowing.

Why it matters

Your environments now stay responsive independently of one another. Development can queue as much work as it likes without pushing production to the back of the line – production keeps processing alongside it. Environments in the same tenant still share one pool of processing capacity, so a genuinely busy tenant can still mean things run a little slower overall, but one environment can no longer block another.

What you need to do

Nothing. Environment-level fairness is already live and applies automatically to every tenant. There's no configuration to enable and no changes needed to your ingest, schemas, or environments.

Questions? Reach out on your support Slack channel or at support@enterspeed.com.