How Could Cloud Telephony Companies Get It So WRONG?
As it was once said, "Those who do not learn history are doomed to repeat it." Guess what, many of the companies who are in the Hosted or Cloud Telephony space are guilty of just that. What they have done is missed the opportunity to get Cloud Telephony correct.
Just by moving the hardware and software to the data center and adding a couple of redundant data centers across the world, does not a reliable and scalable telephony solution make.
With all the evolution and disruption in technology these days, at least these companies could of re-evaluated the design to leverage newer technologies like micro-services and containers. Instead they took the easy path and just moved everything into the "cloud" aka data center(s).
How Microservices and the AWS Platform Are Re-shaping the Idea of Customer Experience
During televised baseball game, Major League Baseball can instantly upscale it’s computing demand to track the trajectory of a baseball and render an image of the trajectory and present it to the live audience in real-time.
Netflix can serve over one billion hours of content a month on tens of thousands of instances of its engine located around the world.
What are the technologies that enable MLB and Netflix provide these experiences to their customers?
Microservices and the Amazon Web Services (AWS) platform.
Together, these two technologies provide the ability to make communications tools that are reliable, easily updated, and massively scalable.
When it comes to a company's communications system, reliability is paramount. If the system isn’t reliable, customer calls are dropped, websites go down, and video conferences with prospective clients “go black”.
So what do Microservices and AWS mean for system reliability?
The highly-decoupled nature of the Microservices architecture brings a high level of resiliency to today’s complex unified communications as a service (UCaaS) systems. This decoupling of services means that, even if an existing service fails, the rest of the system still operates unaffected.
For its part, AWS’s EC2 Cloud computing platform had a 365-day availability of 99.9974% and their S3 Cloud storage platform had a 365-day availability of 99.49%.
Combine the resiliency of the Microservices architecture with AWS’s high availability and you have a one rock-solid system.
Referring back to the decoupled nature of Microservices, the architecture enables fixes and even new functionality to be deployed frequently and without the major interruption that a normal software deployment would cause.
What this means to the customer on this platform, is that the ability to install new features or upgrade existing services in days/weeks versus weeks/months.
Scalability… Both “Macro” and “Micro”
This is where the two technologies together really shine as the architecture that can take advantage of dynamic, real-time scaling needs meets the platform that can provide virtually unlimited computing power.
And because of the decoupled nature of the Microsystem architecture, functionality can be scaled at the whole system level or, if the demand is increased on just a subset of the system’s functionality, at the business-function level.
Who is the one company that got it RIGHT!
I started off this blog with wondering how so many companies that offer cloud based telephony or Unified Communications as a Service go it wrong. Well there is only one company that got it right.
Download the white paper to see how Interactive Intelligence got it right!