Orchestrator: review the architecture to better distribute the load when creating tasks
Description
PRDE - Story default text according to the team DoR (Definition of Ready)
01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
The goal of this card is to split the current orchestrator into 2 applications.
A “controller” app will download the tenants and apps from the platform and schedule the queries that will be executed. Once the schedules are triggered the jobs will be sent to pubsub.
Then we will create a “worker” app that will read from pubsub and process the data.
With this architecture in place we will be able to scale the “workers” in case the number of jobs increase.
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
- Review the architecture of orchestrator.
Activity
Details
Priority
High
@Robson Thanael Poffo ,
@Jonathan Willian Moraes , @Ingo Wagner ,
This issue was planned to be delivered until 2024-04-15. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-04-15, 2024-03-01, 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
Waiting for SRE to deploy and test this.
@Robson Thanael Poffo ,
@Pedro Buzzi , @Ingo Wagner ,
This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-01, 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@Robson Thanael Poffo ,
@Ingo Wagner ,
This issue was planned to be delivered until 2024-03-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.