You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
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
The text was updated successfully, but these errors were encountered: