multitenancy support about rasa HOT 4 CLOSED

Personally I like more the idea of having several models served by one server...although I think that the implications on that over spacy and MITIE would have been well investigated.

So basically you would have a /models/flights or /models/restaurants right? each one of them would then be able to answer queries at /models/flights/parse?q=flight from Tokyo to Munich

from rasa.

Just an idea: use multiprocessing's Process class to spawn processes from a "main" process then use it's Queue class to implement a facade over Spacy, MITIE and anything that has a heavy memory footprint or a long start-up time. That way those things only run in the "main" process, as long as they can be shared.

EDIT: upon second thought, it would be cleaner and just as performant to make Spacy and MITIE microservices themselves.

from rasa.

thanks for the input @baregawi - you guys are on AWS right? so would you run this on elastic beanstalk or just a regular VPS?

from rasa.

For our main servers, we use Flask as our application framework and deploy through AWS CodeDeploy at the moment since our application is not simple enough for Heroku or Elastic Beanstalk. But I imagine that if we contribute models to rasa_nlu they will be our individual ML/NLP modules which are all Python classes at the moment.

from rasa.