apops - Fotolia
Analyst Dave Michels recently examined Avaya's new communications platform as a service spin-off, Zang. In a blog, he writes that at the core of Zang is Esna, the UC integrator Avaya acquired last year, along with the CPaaS offering, a development environment based on Avaya Breeze and Zang Spaces, a persistent chat application originally developed by Esna.
Even though Zang is a wholly owned subsidiary of Avaya, Michels says the degree of independence from Avaya is unclear. He writes that the separation keeps Zang agile and could reduce channel conflict but questions how Zang will be sold and marketed. For instance, will Avaya customers looking for a communications platform as a service (CPaaS) offering be directed to Zang, and will Avaya prioritize Zang Spaces for messaging?
He writes that it is unclear how much of Avaya's portfolio and customer base Zang will be able to leverage, compared to Cisco, which acquired Tropo and integrated the cloud communications API across its collaboration portfolio.
Why organizations consider public cloud adoption
Current Analysis principal analyst Tim Banting discusses the rising trend of public cloud adoption. He writes that public cloud services are a hot topic this year and adoption seems more tangible than in recent years.
Banting says two cloud deployment themes stand out to him. The first trend is that public cloud adoption is not about cost savings. Rather, organizations are going to the cloud to improve agility and competitiveness. Most organizations find the cloud has higher operational costs than an on-premises infrastructure, particularly in the first year of deployment.
The second trend is organizations are going to the cloud to bypass their IT department. He writes that the cloud has few barriers of entry and offers easy implementation and updates. The cloud also streamlines enterprise collaboration, reducing the need to rely heavily on IT.
Read more about why Banting finds some organizations are choosing to stay on-premises.
How to prepare for an SD-WAN implementation
ZK Research principal analyst Zeus Kerravala outlines steps that organizations should take before they implement SD-WAN.
The first step is to ensure infrastructure is ready for an SD-WAN implementation. This includes the necessary updates to hardware and software and making sure infrastructure components are completely SD-WAN-ready before organizations dive into a deployment, he writes.
The second step is to do an application audit. This means organizations must understand what apps traverse the WAN and what the typical traffic patterns are. Organizations should know which apps are subject to network issues, like jitter and latency, and their bandwidth consumption. Kerravala writes that if an organization has a hybrid WAN, they must know which apps run on broadband and on MPLS.
The third step is to change the organizational structure of IT. Kerravala writes that different IT teams -- like the network, application and compute teams -- must work together for an SD-WAN implementation. Applications and compute infrastructure are highly dependent on the network, which means cross-collaboration needs to ensure a good end-user experience.
Learn what other steps Kerravala says enterprises should take for an SD-WAN implementation.
PaaS, storage shine with enterprise cloud adoption
Enterprise public cloud adoption nears tipping point
How SD-WAN offers enterprises control, cost savings