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

Processing Broker and Processing Server #136

Open
tdoan2010 opened this issue Nov 14, 2022 · 0 comments
Open

Processing Broker and Processing Server #136

tdoan2010 opened this issue Nov 14, 2022 · 0 comments
Assignees
Labels

Comments

@tdoan2010
Copy link

tdoan2010 commented Nov 14, 2022

This epic is used to track the progress of the implementation of Processing Broker and Processing Server.

web-api-distributed-queue

Processing Broker features:

  1. Deploy all necessary processing servers and a message queue system (e.g. RabbitMQ) at specified locations via a configuration file. The deployment is either via Docker or native.
  2. Configure the queuing system with specified number of queues. Each processor type should have its own queue, and the queue name is the name of the processor. For example, ocrd-dummy queue for the ocrd-dummy processors.
  3. Accept the incoming requests via REST API and submit a message to the appropriate queue.
  4. Shutdown all processing servers and the message queue if requested or by the end of the OCR process.

Processing Server features:

  1. Listen to the message queue and pull the message.
  2. Save the working status and log to the database.

New specifications

To achieve the mentioned functionalities, 2 new specification must be created:

  1. The schema of the configuration file, which the processing broker takes.
  2. The structure of the message submitted to the queue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants