Apporach 1
Each server calls and other details will be stored on REDIS like below
{
servername:'',
url:'',
callCount: '',
calls:[
{
transcript:'',
userJoined:'',
subscriber:'',
}
]
}
When ever we make call outbound or inbound we need to check from redis which has the callCount less or ok to handle we need pick that server and attach that server URL. calls will use that.
So if we have all server are full then we need to spin up new server trigger event to keda?
What problem
- scable solution easy to maintain and debug
- Error free and zero downtime
- easy to adpat new feature.
company:call:id