DiamondLightSource / DiamondLightSource/daq-queuing-service

Notes from queue discussion

Open
#13 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
1
Avg merge
1d 3h
Merged PRs (30d)
16

Description

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.