As more and more enterprises are turning away from CPE based equipment to cloud-based services, Infrastructure as a Service is becoming more prevalent. One of the key infrastructure nodes that will be required on these enterprise IP-based virtual networks will be SBCs. These SBCs will still be required to serve their traditional roles including securing the network border and media transcoding for the cloud-based services, such as Unified Communications, that they support.
But these SBCs will also need to scale on both private and public networks. Gone are the days you can just bring in “big iron” based on your premise to solve a scalability problem. The virtual SBC itself needs to scale within the cloud. You may have specific high end performance requirements regarding the number of sessions the SBC needs to support on a regular basis, or you may have performance spikes that the cloud-SBC would need to be able to meet. Either way, the SBC in the cloud needs to perform at a high level.
And that means the SBC vendor would need to spend significant effort on this front. It doesn’t just happen “automatically”. Whether the environment is AWS, or OpenStack, or something else, each has specific architectural requirements that must be understood and built into the product.
To learn more about Key Considerations for SBCs in the Cloud, please read this Frost and Sullivan whitepaper.