Hi @mmm3bbb,
I think putting everything in a single instance would cause performance issues in the end and you will loose your overview regarding the needs of your system represented in a single config file.
How about a two step approach:
- Set up a server that provides an API which takes the domain context to.identify the service that holds the particular model for that and passes the request through.
- Setup a docker environment in which a docker-compose file orchestrates every single rasa instance that is needed for the languages (even an action server can be run alongside)
- Pass a given domain context labeled input to its specific docker instance
If both “systems” are placed on one server the http performance (or whatever you might want to use) would be acceptable and you have a highly scalable architecture (CloudFoundry, Kubernetes).
Most important: every language is kept separate which reenables the overview and configuration capabilities.
What do you think?
Regards Julian