Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a workitem enqueuing functionality for the Product Construction Service #3201

Closed
dkurepa opened this issue Jan 15, 2024 · 1 comment
Assignees

Comments

@dkurepa
Copy link
Member

dkurepa commented Jan 15, 2024

The Product Construction Service will work on a workitem based queue. We will have endpoints that will enqueue different types of workitems, and we'll have workers who will take these workitems, and resolve them one by one.

The main reason for choosing this approach is the ability to scale out in the future, and have more workers working at the same time, if need be (we can scale out based on the number of items in the queue).
Based on the official documentation, the most likely candidate for the queue host is the Azure Storage Queue, which, importantly, supports KEDA scaling

@dkurepa dkurepa changed the title Implement a workitem enqueuing endpoint for the Product Construction Service Implement a workitem enqueuing functionality for the Product Construction Service Jan 17, 2024
@dkurepa dkurepa mentioned this issue Jan 17, 2024
3 tasks
@dkurepa
Copy link
Member Author

dkurepa commented Jan 23, 2024

The PR implementing this functionality has been added. We updated the bicep script to create an Azure Storage account with a queue too. When running the service locally, the Azurite Azure Storage will be used automatically.
We haven't implemented any endpoints yet, we'll do that in the future for specific scenarios/workitems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants