# Removing projects for Rasa NLU server

**URL:** <https://forum.rasa.com/t/removing-projects-for-rasa-nlu-server/8962>\
**Category:** Announcements\
**Created:** [April 24, 2019, 10:44am UTC](https://forum.rasa.com/t/removing-projects-for-rasa-nlu-server/8962 "2019-04-24T10:44:51Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![mmm3bbb](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@mmm3bbb](https://forum.rasa.com/u/mmm3bbb)\
**Post date:** [October 21, 2019, 8:26pm UTC](https://forum.rasa.com/t/removing-projects-for-rasa-nlu-server/8962/25 "2019-10-21T20:26:04Z")

</div>

@JulianGerhard Right now I have two Rasa servers (and action servers) running and a Flask app that accepts requests from the app (which includes a scenario id) and routes it to the correct Rasa server’s REST connector.

So I’d replace the two Rasa servers with what you suggest. Definitely worth looking into. I’m a little scared what running 20 Rasa instances plus 20 Action servers times whatever horizontal scaling is required means for system resources though. :-/

I guess one nice thing about this is that I might be able to move some of the smalltalk into a single Rasa model and out of the individual scenario models… and then cache smalltalk results in the Flask app.

---

_[View the full topic](https://forum.rasa.com/t/removing-projects-for-rasa-nlu-server/8962)._