'cisco' Systems’ impressive earnings performance now begs an issue: why has Juniper Systems annual revenue somewhat stalled? Within the last couple of years, Juniper has apparently been playing catch-up in accordance with the heavyweight enterprise networking solution providers. Past non-accretive acquisitions, multiple runs at building out a Wi-Fi portfolio, misses in delivering software-defined networking (SDN) abilities, and difficulty in driving a sustained freeOrAPI-brought development plan are contributors i believe. I’d prefer to dig just a little much deeper in to these areas.
Some acquisitions that merely didn’t pan out
In 2004, Juniper acquired NetScreen Technologies for any staggering $4B available, so that they can shore up its security portfolio. Granted, a great deal has altered within the last fifteen years using the vulnerabilities produced by IoT sensors and also the steady escalation of threats from both outdoors and within network environments. However, customer confidence in Juniper was shaken a couple of years back using the discovery of unauthorized code dating back 2012 that offered like a “backdoor” for decrypting traffic.
This Year, Trapeze Systems guaranteed to create controller virtualization to wireless systems in a cost of $152M, but Juniper abandoned the woking platform for partnerships with Aruba and Ruckus Systems (eventually announcing its intent to get Mist Systems earlier this March). This Year, the organization acquired Contrail Systems for $176M in order to boost its SDN abilities. 5 years later, though, Juniper handed what grew to become OpenContrail off and away to the Linux Foundation if this couldn’t build momentum behind a developer community.
Is free important?
In recent press in the Open Infrastructure Summit that ended earlier this year, Juniper spoke of their participation on view source community. After its change in OpenContrail towards the Linux Foundation, the work was renamed Tungsten Fabric. Juniper still remains involved today. A professional mentioned inside a recent SDxCentral article available here the various free projects still face challenges with customer adoption. Maybe that’s according to Juniper’s historic concentrate on the carrier/telco and repair provider side from the market versus. enterprise. However, within the time I’ve spent at Linux Foundation user group occasions like the DPDK Userspace and Open Network Summits in The United States and Europe, I’ve observed firsthand adoption across both domains (if interested, you'll find my newest article with that subject here).
Overall
It isn't my intention to choose on Juniper. It has told a great story but has fallen somewhat short around the execution. I understand the executives at Mist Systems, plus they do bring some interesting ip towards the table for Juniper. I had been asked to sign up inside a phone briefing with Juniper and Mist soon after the purchase announcement, and that i applaud executives in allowing Mist operational autonomy to carry on its innovation efforts around AI and Wi-Fi. However, I must see Juniper invest more sources in building out a more powerful SDN offering in addition to a developer community by having an API-centric approach. The second won't help the company’s efforts in free but additionally promote innovation on the top of their hardware. One has only to check out the prosperity of Cisco’s DevNet and HPE Aruba’s Airhead communities for examples. These infrastructure providers are coming up with value-add and “stickiness” with funnel partners possibly Juniper might take a webpage using their playbooks
No comments:
Post a Comment