Click here to close now.


Microservices Expo Authors: Elizabeth White, Yeshim Deniz, Carmen Gonzalez, Liz McMillan, Mike Kavis

Related Topics: @CloudExpo, Microservices Expo, Containers Expo Blog, Agile Computing, Cloud Security, SDN Journal

@CloudExpo: Article

Network Neutrality, Victory or Disappointment? | Part 2

This decision looks likely to set the pattern for ISP regulation in the U.S. for some time to come

In my last blog, I discussed the debate surrounding the true definition of open and unfettered Internet, and the different interpretations various groups and individuals have on the matter. In this posting, we continue the discussion.

The U.S. government has not enacted legislation to actually define and require Internet openness or to specify what level of non-openness is acceptable, if any. So openness is a concept without legal definition or backing, which means that individual opinions vary on what constitutes fettering and what doesn't. And attempts by the FCC to fill this gap with the Open Internet Order triggered this court action.

The debate, as constructed just now, offers two alternatives: Do ISPs have the right to manage Internet traffic preferentially, thus by most definitions fettering that traffic? Or do governments have the right to prevent ISPs from managing Internet traffic preferentially, thus clearly fettering the Internet by engaging in regulation of its players?

The FCC in the past has held the view that regulating the ISPs to prevent fettering is a lesser evil than allowing the ISPs to manage their traffic.

The recent U.S. federal court decision agreed with the ISPs that the FCC should not regulate ISP activity. Note that this decision is not based on the pros and cons of openness, but on the limits to the authority of the FCC. The court stated, "Our task as a reviewing court is not to assess the wisdom of the Open Internet Order regulations, but rather to determine whether the Commission has demonstrated that the regulations fall within the scope of its statutory grant of authority."

Whatever the reason, it seems that ISPs are now free to offer preferential quality of service to edge providers and edge providers are free to pay them money for the privilege.

What can happen next? Taking this to the U.S. Supreme Court is something that pro-neutrality advocates must be considering, but since the issue is not about neutrality, but rather FCC jurisdiction, the chances of success are likely to be slim.

What about a move to change the scope of FCC jurisdiction? This could be achieved by legislation that specifically defines Internet openness, makes it a legal requirement and empowers the FCC to oversee it. Not much chance of that happening anytime soon.

Alternatively, the FCC could make the case that Internet access should be defined as a common carrier service, which would make it subject to the same kind of oversight as traditional phone services. Judge Silberman in his (partially) dissenting opinion fears this possible consequence, while the New York Times encourages the FCC to go for it. Why the difference? Apparently Silberman dislikes government regulation more than he dislikes corporate manipulation of Internet traffic, while the New York Times just happens to take the contrary view. The divisions continue, and it seems that extending the jurisdiction of this FCC ruling in this way is not much more likely than new legislation.

Altogether, this decision looks likely to set the pattern for ISP regulation in the U.S. for some time to come, and we should start thinking about the implications it will have on the future. If we look closely, we may find that for the winners in this case, it may turn out not to be such a big deal after all, and those who view this as an unmitigated disaster may be relieved that it's not as bad as they feared.

If this decision stands, as seems likely, there are a number of possible repercussions to consider. In what ways will the ISP competitive landscape be transformed? How will edge providers respond? How does the role of applications change in a world in which fettering is normal, and how will that impact the software companies? Will there be a knock-on effect on the venerable institution of inter-ISP peering charges? And what will be the impact on the billing needs of all these players in a world made much more complex?

Leave a comment to let us know where you think these new developments will lead us.

More Stories By Esmeralda Swartz

Esmeralda Swartz is CMO of MetraTech, now part of Ericsson. She has spent 15 years as a marketing, product management, and business development technology executive bringing disruptive technologies and companies to market. Esmeralda is responsible for go-to-market strategy and execution, product marketing, product management, business development and partner programs. Prior to MetraTech, Esmeralda was co-founder, Vice President of Marketing and Business Development at Lightwolf Technologies, a big data management startup. She was previously co-founder and Senior Vice President of Marketing and Business Development of Soapstone Networks, a developer of OSS software, now part of Extreme Networks (Nasdaq:EXTR). At Avici Systems (Nasdaq:AVCI), Esmeralda was Vice President of Marketing for the networking pioneer from startup through its successful IPO. Early in her career, she was a Director at IDC, where she led the network consulting practice and worked with startup and leading software and hardware companies, and Wall Street clients on product and market strategies. Esmeralda holds a Bachelor of Science with a concentration in Marketing and International Business from Northeastern University.

You can view her other blogs at

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@MicroservicesExpo Stories
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production? In his session at DevOps Summit, Fred Simon, Co-founder and Chief Architect of JFrog, will demonstrate how to implement a promotion model for Docker images using a binary repository, and then show h...
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Our guest on the podcast this week is Jason Bloomberg, President at Intellyx. When we build services we want them to be lightweight, stateless and scalable while doing one thing really well. In today's cloud world, we're revisiting what to takes to make a good service in the first place. Listen in to learn why following "the book" doesn't necessarily mean that you're solving key business problems.
Achim Weiss is Chief Executive Officer and co-founder of ProfitBricks. In 1995, he broke off his studies to co-found the web hosting company "Schlund+Partner." The company "Schlund+Partner" later became the 1&1 web hosting product line. From 1995 to 2008, he was the technical director for several important projects: the largest web hosting platform in the world, the second largest DSL platform, a video on-demand delivery network, the largest eMail backend in Europe, and a universal billing syste...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively.
For it to be SOA – let alone SOA done right – we need to pin down just what "SOA done wrong" might be. First-generation SOA with Web Services and ESBs, perhaps? But then there's second-generation, REST-based SOA. More lightweight and cloud-friendly, but many REST-based SOA practices predate the microservices wave. Today, microservices and containers go hand in hand – only the details of "container-oriented architecture" are largely on the drawing board – and are not likely to look much like S...
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.
All we need to do is have our teams self-organize, and behold! Emergent design and/or architecture springs up out of the nothingness! If only it were that easy, right? I follow in the footsteps of so many people who have long wondered at the meanings of such simple words, as though they were dogma from on high. Emerge? Self-organizing? Profound, to be sure. But what do we really make of this sentence?
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.
There once was a time when testers operated on their own, in isolation. They’d huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they’d wait for the developers in the other room to fix the bugs they found, yet they’d frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particula...
Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like t...
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery ...
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at @DevOpsSummit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.