dcsimg

Creating an App-Centric Network for the Internet of Things

  • Creating an App-Centric Network for the Internet of Things-

    Modern Load Balancing

    NFV (Network Functions Virtualization)

    NFV decouples basic network functions, including firewalling, network address translation (NAT), load balancing and security filtering from running in hardware and application specific integrated circuits (ASICs) to run in software, making it easy to increase scalability and boost performance, as administrators or automation software can quickly and easily allocate new resources.

    Since IoT encompasses devices that could be anywhere, connected via any network, the ability to replace costly hardware in fixed locations with software provides optimum flexibility. NFV services can be configured on the fly, so management software can dynamically improve the user experience and meet QoS requirements.

    NFV service chaining refers to all of the virtual physical devices and software-based services required to connect all parts of an application, from the router to load balancer to multiple application servers, database servers, Web servers and other NFV services, like WAF (Web application firewall).

    There may be many IoT devices scattered across data centers and cloud providers. Provisioning and monitoring the service chain is costly and time-consuming, especially with proprietary networking hardware, a variety of operating systems, and a mix of vendor-specific management tools. Service chaining is more easily enabled with NFV because virtualized network functions can be provisioned and re-provisioned entirely through software, to support the workload or customer requirements. These technologies – advanced load balancers or ADCs, NFV and service chaining – are well suited for the ever growing Internet of Things economy.

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13

Creating an App-Centric Network for the Internet of Things

  • 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13
  • Creating an App-Centric Network for the Internet of Things-12

    Modern Load Balancing

    NFV (Network Functions Virtualization)

    NFV decouples basic network functions, including firewalling, network address translation (NAT), load balancing and security filtering from running in hardware and application specific integrated circuits (ASICs) to run in software, making it easy to increase scalability and boost performance, as administrators or automation software can quickly and easily allocate new resources.

    Since IoT encompasses devices that could be anywhere, connected via any network, the ability to replace costly hardware in fixed locations with software provides optimum flexibility. NFV services can be configured on the fly, so management software can dynamically improve the user experience and meet QoS requirements.

    NFV service chaining refers to all of the virtual physical devices and software-based services required to connect all parts of an application, from the router to load balancer to multiple application servers, database servers, Web servers and other NFV services, like WAF (Web application firewall).

    There may be many IoT devices scattered across data centers and cloud providers. Provisioning and monitoring the service chain is costly and time-consuming, especially with proprietary networking hardware, a variety of operating systems, and a mix of vendor-specific management tools. Service chaining is more easily enabled with NFV because virtualized network functions can be provisioned and re-provisioned entirely through software, to support the workload or customer requirements. These technologies – advanced load balancers or ADCs, NFV and service chaining – are well suited for the ever growing Internet of Things economy.

The Internet of Things (IoT) is not just the connected refrigerator. It's thousands of medical devices in hospitals, smart utility meters, GPS-based location systems, fitness trackers, toll readers, motion detector security cameras, smoke detectors, and last but not least, embedded systems. Each of these IoT end nodes requires connectivity, processing and storage, some local and some in the cloud. This means scalability and application elasticity to adapt to dynamic requirements and ever-changing workloads.

To support and accommodate all the devices, sensors and other network-connected gadgets that will eventually become part of the IoT, network designs will need to adapt and become more application centric, according to KEMP Technologies. From health care to automotive and manufacturing to consumer electronics, the Internet of Things is a quantum revolution in how we think about application data activity. Is your network ready for the application onslaught that's coming?