When you were young, a cloud was a cloud. Then you learned that cumulus meant fair weather, while nimbus meant rain, and funnel cloud meant run for cover. Cloud computing has a simple appeal, but it also has layers of complexity that can make the difference between a nice day and a flood of problems.
Sticking to the core issues
We’re not going to get into the practical or semantic differences between cloud computing and SaaS (as well as PaaS , IaaS, and HaaS). Others have done better at that than we have. There’s a pretty readable one at VentureBeat. For our discussion, we are going to assume that you are interested in a cloud-based contact center and want to know how to differentiate good from bad cloud offerings.
Why a cloud solution?
The reasons for moving to cloud computing solutions are also much better covered elsewhere, but here’s a quick summary:
A generation worth skipping
Bright Pattern has established the fifth wave of contact center technology.
Sure, it was the only game in town for a while, but now that the first true cloud contact solution—Service Pattern– is available, why settle for a partial solution?
What a real cloud solution looks like
The Bright Pattern team has been in this business for a long time. In fact, the core engineering team is that same one that built the contact center application that you are probably using today. When our co-founders discussed the idea of creating the next generation of contact center, they knew it would be cloud-based. But more importantly, they knew that migrating or integrating existing code would not work and that they would have to start over to do it right. And because none of the established vendors were willing to abandon their technology and customer bases, they knew that they’d have to start a new company. That gave them the freedom to develop this cloud solution as it should be—from the ground up.
The advantages of multitenancy
Multitenancy is an important element of effective and efficient cloud computing. Among the advantages of a multitenant architecture are:
But is it real multitenancy?
Many of our competitors stretch the definition of multitenancy. And the reason is obvious, they migrated their old on-premise installation-based code into a pseudo-cloud. They had no choice. They are multitenant at the datacenter level, but not at the process level. In other words, they are still provisioning a single real or virtual server to each client, which is really the same old less efficient and more costly model. They are inherently less scalable and less cost-effective, and it is harder for them to roll out updates. Really, all they have done is to change management responsibility, not how it works.
Public clouds, private clouds, on-premises, and hybrids
The ServicePattern solution supports freedom of choice in deployments.
Or choose a hybrid solution when a combination of architectures makes sense. For example, if you have a solid relationship and contract with a carrier for voice, you might want your RTP and SIP on site, wile the rest of the solution is accessed by your agents through the public cloud.
The bottom line
If you want a true cloud contact solution, you won’t get it anywhere else. Other vendors’ multitenancy strategy is to set up another box. A number of vendors simply can’t do private instances (possibly a security or regulatory concern). And while the cloud vendors can’t get on-premise, and the on-premise vendors can’t do cloud, we offer both and hybrid to boot.