During a discussion with core and other teams it was decided that the best way to move forward with the queuing service is to split up the queue and worker. The queue will:
- Convert between experiment definition and blueapi call
- Have an internal order
- Be backed by a database for persistence
- Have a
get_next_task endpoint which returns the task at the top of the queue
The worker will call get_next_task and call blueapi as a separate service.
Sub-issues should be created for all of the above that don't match the current architecture.
Acceptance Criteria
- The queue and worker are seperated
- The queue architecture matches the points above
During a discussion with core and other teams it was decided that the best way to move forward with the queuing service is to split up the queue and worker. The queue will:
get_next_taskendpoint which returns the task at the top of the queueThe worker will call
get_next_taskand call blueapi as a separate service.Sub-issues should be created for all of the above that don't match the current architecture.
Acceptance Criteria