Apple, Amazon, Tesla Motors… we have come to associate these company names with creative ideas, innovative approaches, and game-changing products and services. These names have become synonymous with transformation, breaking the rules, and doing things differently. But these famous names also often have a meaning, an underlying reason why the founders chose them. Tesla, of course, pays homage to a Serbian inventor who was known for his vision and genius. Patagonia wanted to invoke romantic visions of glaciers. Red Bull energy drink’s creators came up with a name that symbolizes the bull’s power and perseverance.
So, how did the AppViewX name come to be and what does the “X” stand for?
Let’s start with the AppView part, which – you guessed it – means that we believe in having an application-centric view of the enterprise IT infrastructure. All that datacenter technology – routers, switches, firewalls, load balancers, proxy servers, etc., exists for one main purpose only – to support applications that run the business. Companies that adopt the device-centric view often find their teams working in silos, lacking efficiency, increasing potential risks of failure and driving up costs.
And if in the past applications were deployed once every few months, today’s continuous delivery practices mean that changes and upgrades are rolled out almost daily, triggering the need for changes in the underlying application service infrastructure. To make the latest application releases available to the end-users as fast as possible, DevOps and NetOps teams need to respond quickly to a variety of change requests. Which brings us to the “X” part of our name.
Just like in math, the letter “X” stands for the variable. In some cases, it’s a simple value, in others, it depends on other variables. At AppViewX, we take an application-centric approach to a number of tasks (“variables”) related to running the enterprise network infrastructure, including monitoring, managing, automation, orchestration, self-service, and more. The AppViewX platform gives NetOps and DevOps teams a complete view of their infrastructure, shows them the current state of application health, status and performance, helps diagnose and troubleshoot outages in a contextually-aware manner, and gives teams the ability to self-service and build automation workflows.
Our journey started with building a low-code platform for automating and orchestrating changes in the load balancing infrastructure. The initial success led us to extend our solutions to include additional elements of the network. Today, our customers enjoy the ability to manage complex infrastructure spanning multiple vendors and architectures, and design and implement automation workflows for each network component. That’s the power of “X” – whether it’s different components (load balancers or switches, certificates or keys), network layers (L2 or L7), architectures (on-premise, hybrid, multi-cloud, or microservices), or operations, (DevOps, NetOps and SecOps orchestration), AppViewX helps enterprises manage it all using intuitive, visual workflows.
In the next blog, we are going to explore how companies can increase operational efficiency by automating up to 90% of their service requests, saving on labor costs, reducing issue resolution times, and freeing up IT resources to focus on more strategic tasks.