SDNs such as control/ data plane separation, virtualization, SDN controllers, and data center concept. The NVF and SDF shares similar goals but both have different working strategies. The statement that "Due to recent network focused advancements in PC hardware, any service that is able to be delivered on proprietary, application-specific hardware should be able to be done on a virtual machine" summarizes the entire evolution of Network Function Virtualization. Nowadays, a number of network devices viz. Routers, Firewalls, Load Balancers and SO on are running virtualized on commodity hardware (Noble, 2017). With a clear objective of reducing equipment costs and decreasing time to market, NFV achieves elasticity and scalability along with strong ecosystem. The SDN also breaks the bond that relates the control/application software with the hardware. Both the architectures- NFV and SDN need optimization at carrier scale of the dynamic cloud environment (Benington, 2014). For achieving greater agility, SDN and NFV aim to control automation and virtualization. Whereas optimizing the deployment of network functions (such as DNS, load balancers, firewalls etc.) was the main intention of NFV. The physical as well as the virtual layers that enable to interconnect virtual network function Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Virtualizing Network Functions in Software-Defined Networks Figure 1. SDN and NFV Relationship Today-Separate Network Tomorrow-NFV: Each Function Appliances for Each function Virtualized Router Router Firewall Firewall Load Balancer Balancer Distribution Switch vSwitch Web Server Web Server Web Server Multiple Blade Servers or Large Hypervisors Power Usage-40A Power Usage=20A endpoints require large-scale dynamic network connectivity to be deployed (Nunes et al., 2014) Network Function Virtualization finds its roots in several previously described network operations problems, especially the implications of bundling services by network equipment manufactu