Closed kamyarghajar closed 1 year ago
Exalate commented:
sara-tagger commented:
Thanks for submitting this feature request
Exalate commented:
TyDunn commented:
Hi @KamyarGhajar. Can you help me understand how and why you are using Rasa a microservice?
Exalate commented:
KamyarGhajar commented:
Hi @TyDunn . We use Rasa NLU as a sequence tagger and intent classifier in our services. In a micro-service architecture using a restful api is not that efficient you know specially when in a Kubernetes cloud solution with several Rasa pods running alongside each other.
➤ Maxime Verger commented:
:bulb: Heads up! We're moving issues to Jira: https://rasa-open-source.atlassian.net/browse/OSS.
From now on, this Jira board is the place where you can browse (without an account) and create issues (you'll need a free Jira account for that). This GitHub issue has already been migrated to Jira and will be closed on January 9th, 2023. Do not forget to subscribe to the corresponding Jira issue!
:arrow_right: More information in the forum: https://forum.rasa.com/t/migration-of-rasa-oss-issues-to-jira/56569.
Description of Problem: For too many concurrent requests, when using RASA as a micro-service, many HTTP API calls and consequently opening many tcp sockets is not efficient.
Overview of the Solution: NATS is a high performance messaging system that can work with a pub/sub architecture. Supporting the NATS subscriber in RASA helps optimizing the performance of the system and gain higher throughputs from RASA.