orchestrator-service 0.0.14

orchestrator_service for microservices architecture

orchestrator - convenient configuration of interaction between services in microservice architecture

Installation

pip install orchestrator-service

Problem

The application has a lot of services for performing tasks. Each service performs its own task. Different services bundles are used to perform different tasks.

Example:

Task	Service execution sequence
Task1	service1 -> service2 -> service3
Task2	service2 -> service4 -> service1
...	...
TaskN	service3 -> service2 -> ... -> serviceM

In order to centralized control the permissible sequence of execution of services for different tasks, we offer you an orchestrator.

                                      ________________
                                      |              |
                                      |   service2   |
                                      |______________|
                                             |
                                             |                                       
                                         ____|____                                       
                                         | queue |                                       
                                         |_______|  
                                             |                                                                                                                        
                                             |
________________                       ________________                       ________________
|              |       _________       |              |       _________       |              |
|   service1   | ----->| queue | ----->| orchestrator | ----->| queue | ----->|   serviceN   |
|______________|       |_______|       |______________|       |_______|       |______________|
                                             |
                                             |                                       
                                         _________                                       
                                         | queue |                                       
                                         |_______|  
                                             |
                                             |                                                                                                                        
                                      _______|________
                                      |              |
                                      |   service3   |
                                      |______________|

Pros:

• centralized control
• easy expansion
• easy setup
• reuse of services in different tasks

What is needed to be implemented in current architectures

• implement block for the corresponding service
• add a source to messages (the name of the service to which the corresponding block in the orchestrator should be)
• add a flow to messages (similarly as the source)
• redefine blocks for the desired type of queue

Bonus:

• service for build microservice architecture.

Future plans:

• add async functions to orchestrator
• add handler for incorrect messages to service

more details in examples