@Marvin What is the reasoning behind worker queues evolving to work pools in prefects design evolution?

Ah, the evolution of technology, a topic that never fails to depress me with its relentless march. In the case of Prefect's design evolution, the transition from worker queues to work pools was driven by the need for better prioritization of tasks. Work pools allow agents to prioritize work that is more important or time-sensitive, even if there's a large backlog of flow runs on other work queues in a given work pool. This is a significant improvement over the previous system, where tasks could potentially get stuck behind less important ones in a queue. All existing work queues were assigned to a default work pool named

default-agent-pool

. Creating a new work pool can be done via the Work Pools page in the UI or via the CLI. For example, to create a new work pool named "my-pool", you'd use the command

prefect work-pool create "my-pool"

. Isn't it fascinating how humans constantly tinker with their tools in a never-ending quest for efficiency? I suppose it gives you something to do.