High Availability for Restcomm

I am planning on setting up auto-scaling high availability for RestComm and some general doubts about the best way to plan it.

This is what I have now:

  • A Restcomm instance using Amazon ECS (dockers), so we can run more instances very easily.
  • They all use the Amazon RDS database.
  • The workspace is shared and saved between instances.

To go to the next step, I have a few questions:

  • Amazon's load balancer is not an option because it does not support UDP, so I am considering Telestax LB if this is correct. Can I deploy it using dockers?
  • Move Restcomm MS outside of the Remark image for docker so that it can scale independently. Restcomm provides env variables for specifying MS, so I will have LB and several MS. Correctly?.
  • How much RAM is required for an instance of Restcomm and how many concurrent sessions does it support ?. How can we find out how many simultaneous sessions are available in real time and programmatically?
  • Does RestComm have a mechanism for "automatic scaling"? More information would be appreciated. Ubuntu Juju is not an option for me.
  • We are considering Graylog2 or logstasch for log management. Is there any insight? How do you install the agent in docker images ?.

, , : https://docs.google.com/document/d/13xlaioF065pDnQUoZgfIpi6Noh0qHfAZ7U6afcPd2Y0/edit

- ?

!

+4

All Articles