“Network as a service” is one of those baffling terms the connectivity business periodically comes up that in many ways defies explanation.
After all, the traditional connectivity service is, in fact, “a service.” That noted, enterprises often have ways to “create their own services” using their own infrastructure, as when they use private branch exchanges (phone systems), create their own edge-based software-defined wide area networks or their own virtual private networks.
In such cases, “connectivity” might be called a “product” created by the user, not a service supplied by a connectivity provider. Enterprises can use phone systems to “create their own voice services” or their own edge-based SD-WAN or VPNs, for example.
Definitions of “NaaS” often focus on “cloud based” or “on demand” or “pay as you go” or “pay only for what you use” concepts, and those are generally apt concepts.
So some of us might argue that NaaS) simply restates the older goal of an automated, flexible, on-demand architecture for telecom services that allows customers to add features and services easily and fast; scale usage up and down.
The concept also means the network operator can scale features and services on and off; bandwidth up or down “on demand,” easily and fast in response to customer demand or desires.
So NaaS is simply a new way of stating the older goal of a flexible, automated, scalable network.
No comments:
Post a Comment