Sales +1-855-261-3391 Chat Blog Partner Support Status  |  Download

Networking Unplugged

Perspectives on cloud networking and software-defined WANs

Posted June 27, 2014
Comments 0 Comments

What Would Networking Look Like Today if it Were Built by Cloud Guys?

Pertino is sponsoring DevOpsDays in Mountain View this week, and as we plan for the show I’m reminded of the AWS re:invent conference last November. A couple of the engineers and I attended re:invent and were amazed by the pace at which Amazon is delivering innovative new products as well as the vendors that are building new technology on top of the AWS platform. There is a feedback loop of innovation happening where companies are building products and services that make it easier for other companies to build products and services.  For example, PagerDuty uses Amazon to provide services to Pertino, and Pertino in turn uses PagerDuty to monitor our cloud services. Every year it gets easier and less expensive for companies to create new services and bring them to market because of this loop.

But something struck me at the show. The ease-of-use and flexibility of cloud compute seemed to come to a screeching halt when it came to building the networks to support these systems. There were several sessions with “How To” talks on configuring multi-region and multi-provider private networking solutions. Something was wrong. We can deploy servers all over the world with the click of a mouse. We can add RAM, CPU and infinite storage capacity in seconds. But if we try to connect these machines together as part of a virtual private cloud, we are suddenly back in the world of IP-subnetting, command-line router configurations and IPSec tunnels. What happened to the innovation? Are we taking the networking technology of 15 years ago, removing the sheet-metal and calling it done? 

What would networking look like today if it were built by cloud guys?

If cloud guys reinvented networking solutions today, it would have all of the qualities of cloud-compute. It would be easy to use and deployable in minutes. It would be highly scalable and resilient. It would be delivered as a service at economical prices. It would be a platform for additional services that can be added as needed. Behind the scenes. it would be fully instrumented, monitored and automated. And when the inevitable hardware failures occur, the service would work around the issues to minimize impact to the end-user. In short, it would be Pertino.

Pertino was built from scratch, inspired by the elasticity and power of the cloud, to make networking as effortless as launching a new VM. Amazon manages servers so you don’t have to, and Pertino builds networks so you don’t have to.

Interested in learning more about Pertino and using it to enable your Virtual Private Cloud? Linux version options, installation scripts and more are available—give it a try for free.

Scott Hankins

Scott Hankins

Co-Founder & CTO

Before coming to Silicon Valley for some excitement, I spent seven years building robots at NASA. Developed core networking technology, filed four patents, and ran the deep packet inspection team at Packeteer. From there, I took some time off to explore some ideas, one of which turned into Pertino.

comments powered by Disqus
Chat now Click to Chat