Bot Framework Dispatch CLI replacement with Orchestrator

Hey everyone,

As the Dispatch CLI will be deprecated on December 31, 2021, we've started evaluating Orchestrator as an alternative to it. Information about Dispatch CLI https://github.com/Microsoft/botbuilder-tools/tree/master/packages/Dispatch.

We were using Dispatch CLI basically as a high-level router for our bot that will route the occurrence (text) to the correct resource (Luis, QnA) and produce a resource-specific intent. Also, we are retraining it periodically so the dispatcher will always have the up-to-date data from all resources so it will route to the correct resource.

So, wanted to ask – what is the strategy of using an orchestrator in the current flow? We are able to retrain it with https://github.com/microsoft/botframework-clibut we don't wanna restart the bot after refreshing the orchestrator. Also, how can we use the same trained orchestrator model in multiple bots? (as I understood it's not a trained Luis app)

developer

microsoft teams

Nivedipa-MSFT
Dec 14, 2021
MykolaMedynskiy

1.Orchestrator is a local resource, so is deployed to the target environment. It should require significantly less training than a LUIS model, so should really only be updated along with your source code. But yes, since the model is loaded into memory you need to restart the bot.

2.Deploy the trained model to the desired environments

Please go through below doc for implementation details:

https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-tutorial-orchestrator

Thanks,

Nivedipa

------------------------------------------------------------------------------------------------------------------------

If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.

Forum Discussion

Bot Framework Dispatch CLI replacement with Orchestrator

7 Replies

Resources