SDN Focus is brought to you in partnership with:

Mitch Pronschinske is a Senior Content Analyst at DZone. That means he writes and searches for the finest developer content in the land so that you don't have to. He often eats peanut butter and bananas, likes to make his own ringtones, enjoys card and board games, and is married to an underwear model. Mitch is a DZone Zone Leader and has posted 2573 posts at DZone. You can read more from them at their website. View Full User Profile

The IoC Metaphor in SDN

01.01.2014
| 8244 views |
  • submit to reddit

You're probably familiar with the Inversion of Control pattern that became popular in the last decade.  It hands control of the application's flow of execution over to user events (i.e. event-driven applications).  Lori MacVittie sees some software-defined networking models taking a similar approach and giving control to the applications on the network, but many models of SDN still keep the network in the driver's seat with SDN controllers using an OpenFlow-based model.

The network (the SDN controller in an OpenFlow-based model) makes the decision where to reroute traffic upon encountering a problem. It is still in control and the application itself has absolutely no input in current SDN models. Even in proposed service chaining models, applications are not in control of the flow. The network remains the final arbiter of where and how traffic flows through the network…

… But as SDN controllers have no visibility above layer 4 (IP and port) it cannot recognize content types or that its decisions are inefficient and wasteful.

-- Lori MacVittie


Lori MacVittie's articles are always a good read, so check them out.