mmunication (Route Flow, 2015) RouteFlow relies on technology such as: OpenFlow-enabled switches that be able software-based (such as Mininet) or hardware-based (such as NetFPGAs) OpenFlow controllers such as POX and Ryu, that be used to join the switches to the RFServer The Quagga routing engine can be used in the virtual equipment to give routing services Open vSwitch is used to attach the virtual machines MongoDB is used to give a centralized database for the system and also to implement an IPC service LXC containers as virtual machines intended for running the RFClient and Quagga (CPqD, n.d.). CONCLUSION The idea of a programmable network in the beginning took shape as dynamic networking, which espoused many of the same visions as SDN but lacked both a clear use case and an incremental deployment path. After the era of active-networking do research projects, the pendulum swung from vision to practicality, in the form of sorting out the data and control planes to make the set of connections easier to manage. This work focused for the most part on better ways to route network traffic-a much narrower vision than earlier work on active networking. Ultimately, the work on OpenFlow and network operating systems struck the right sense of balance between vision and expediency. This work advocated network-wide control for a wide range of applications, yet relied only on the accessible capabilities of switch chipsets. Backward compatibility with existing switch hardware appealed to many tools vendors clamoring to compete in the rising market in data-center networks. The balance of a broad, clear vision with a practical strategy for widespread adoption gained traction when SDN found a compelling use case in network virtualization. As SDN continues Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 SDN Controller to develop, its the past has important lessons to teach. First, SDN technologies will live or die based on "use pulls." Although SDN is often heralded as the solution to all ne