You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we had explored NATS queue and I think we can leverage it for horizontal scaling of agent. Here's how the overall architecture would look like:
This architecture demonstrates a horizontally scalable system where multiple credo-agent instances consume messages from a central NATS server in a controlled and distributed manner using queue groups.
What advantages do we get:
Horizontal scaling of controller
Reuse existing NATS infra (if suitable)
Avoid API calls to the controller
An added NATS authentication (security)layer on top of the existing API key
Blockers (might have)
Request received from agent to agent might need to be additionally load-balanced between the inbound endpoint for agents
Database sync between the agents need to be considered
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What
Currently we had explored NATS queue and I think we can leverage it for horizontal scaling of agent. Here's how the overall architecture would look like:
This architecture demonstrates a horizontally scalable system where multiple
credo-agentinstances consume messages from a central NATS server in a controlled and distributed manner using queue groups.What advantages do we get:
Blockers (might have)
References
Read more about NATS queue here: https://docs.nats.io/nats-concepts/core-nats/queue
Beta Was this translation helpful? Give feedback.
All reactions