{"id":4353,"date":"2020-01-07T14:27:04","date_gmt":"2020-01-07T22:27:04","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=4353"},"modified":"2020-08-03T11:20:45","modified_gmt":"2020-08-03T18:20:45","slug":"lets-get-gartner-sase","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/company\/lets-get-gartner-sase\/","title":{"rendered":"Let\u2019s Get SASE"},"content":{"rendered":"

Have you been to a DMV office recently? You take a ticket and wait. You get called to a window and then are told to go to a different window. You take a ticket and wait. And so on. The same sort of waiting game happens to network traffic as it passes through infrastructure based on virtual network functions (VNF). Fortunately, its newer counterpart, cloud-native functions (CNF) is far faster and more efficient.<\/p>\n

CNF is an important component of SASE<\/a> networks. If you\u2019re not yet familiar with it, SASE (secure access service edge) is a new model for network architectures proposed by Gartner that is reshaping the way organizations manage and secure their networks. Gartner SASE<\/a> is a response to the growing need for network & security architectures that are more fluid at the WAN edge.<\/p>\n

SASE<\/a> is first and foremost a cloud-native concept. The need for flexibility and speed requires a cloud-native foundation. VNF implementations cannot provide the levels of agility, scalability and low latency required at the WAN edge. CNFs are more suitable to meet these needs.<\/p>\n

CNFs: Lightweight and Faster than VNFs<\/strong><\/p>\n

A VNF is a software implementation of a network function that runs on one or more virtual machines (VMs) on bespoke or white box hardware. VMs can be linked together to form service chains that support full-scale networking communication services. That\u2019s where the DMV experience begins (Fig. 1). It starts when significant overheads for VM spin up and spin down. Next comes service chain orchestration\u2014take a ticket<\/em>\u2014followed by VM-to-VM handoffs and their resulting hop-by-hop latency\u2014move to the next window, take another ticket. <\/em>The whole process then repeats all the way through the chain. Latency is built into the architecture.<\/p>\n

\"\"<\/p>\n

Figure 1: VNF and its \u201ctake a ticket and wait\u201d experience versus highly streamlined CNF<\/p>\n

In contrast, a CNF is a lightweight container-based software network function that enables spin up and spin down to proceed much faster. Once a container is spun up, traffic is processed, and policies are applied all in a single pass. No more tickets, no additional windows, minimal latency. <\/em>As a member of the Cloud Native Computing Foundation<\/a> (CNCF), it is our mission at Infoblox to make cloud-native computing ubiquitous for foundational network services.<\/p>\n

The CNCF site<\/a> provides real-world examples of how CNF implementations save time and money. Here are just a few:<\/p>\n