Earlier this month, F5 announced its ScaleN architecture designed to make it easier for companies to deploy a software defined network and extend virtual networks to the cloud. ScaleN can be thought of as a unified set of virtual and physical infrastructure that has been configured to optimize SDN environments. ScaleN also provides a new feature called iCall, which is an extension of its popular iRules scripting language and gives F5 ADCs the capability of dynamically reconfiguring based on the real-time status of the ADC infrastructure. The iCall technology allows for applications or networks to interface with the ADCs to trigger the reconfiguration.
Looking at this functionality, it’s easy to see that there’s significant overlap with traditional SDN controllers. One of the value propositions of SDNs is that the controllers offer a set of northbound application programming interfaces (APIs) that give applications more control of the network. F5’s iRules has given customers the ability to create custom features to handle network and application events. But iCall brings automation to F5 infrastructure, removing the need for manual intervention. It would seem that much of the value of the SDN controller is being wrapped into the ADC, and why not? The application delivery infrastructure already sits between the network and application tiers, similarly to how many of the SDN controller vendors position their products.