At KEMP Technologies, we understand our customer’s businesses and the applications needed to support them. Through careful discovery and analysis, we take the time to understand each application workflow and business processes used. We realize that our customer’s application environments are diverse whether they be on-premises, hybrid or in the cloud. We are seeing an increase in multi-cloud strategies across various industry verticals whether it be for legacy or modern applications or both.
It’s always important to mention that security should always be top of mind before, during and after application development but also shouldn’t be limited to just the applications themselves. A good defense in depth strategy will encompass many facets involving people, process and technology. Applications also need performance, availability, and manageability. KEMP Application Delivery Controllers (ADCs) can be deployed wherever your applications live: in the cloud, on-premises or in hybrid environments. There are also flexible licensing options based on your exact needs. With KEMP’s Metered Licensing, customers license their KEMP Virtual LoadMasters based on aggregate throughput used. This means that an unlimited number of Virtual LoadMaster instances can be deployed but the actual charges that will be billed will be based on the peak monthly usage for all instances. The cost savings for customers who take advantage of this licensing model can be substantial and we are seeing an increase in the move to OPEX (operating expenses) versus traditional CAPEX (capital expenditures) when moving to cloud and/or hybrid models of operation. Perpetual licensing is still very relevant and will continue to be a viable option for customers. From an operations management perspective, we have many customers who have taken advantage our KEMP 360 Central platform to provide full load balancing application monitoring and manageability in a simple-to-use web interface.
Let’s look at a real-world example that ties together all of the features discussed above. In the screen shot above, we have KEMP 360 Central deployed in Microsoft Azure. This large global enterprise customer scenario involves several applications running and our KEMP Virtual Loadmasters are deployed in front of each to provide availability, security, and manageability. There are three perpetually licensed Virtual LoadMaster instances deployed in two Amazon Web Services regions, one perpetual Virtual LoadMaster deployed in Azure Stack in New York, and a Metered Licensing Virtual LoadMaster Pair configured for High Availability to support Virtual Desktop Interface (VDI) in Azure West and a perpetual Virtual LoadMaster instance is used by a DevOps team in Azure East. Finally, there are three remaining instances that are important to mention here; KEMP 360 supports third party load balancers and in the picture, you see that our customer has NGINX, HAPROXY and F5 configured within KEMP 360 Central. KEMP also support AWS Elastic Load Balancer too.
The benefits of this configuration are as follows:
1) Single view of the entire ADC estate company-wide and the applications that they are load balancing, including third-party ADC vendors
2) Ability to see, in real-time, application health and act to resolve issues such as downed real servers
3) Full manageability of KEMP ADC instances; firmware updates, VS configuration, application health, template management, local ADC license activation, role-based user access (RBAC), Metered License usage reports, and much more.
4) Perpetual and Metered Licensing LoadMaster types are visible and managed by KEMP 360 Central
In the example above, each ADC instance was aptly named based on the usage that this global enterprise customer felt applicable for their specific scenario. The point here is that the flexibility of KEMP 360 means it can be configured to use the naming convention your company uses.
Let’s change things up a bit and showcase how a similar scenario would work at a Service Provider (xSP). In the screen shot above, the same load balancer instance names are used however instead of a multi-cloud naming approach like the global enterprise customer, this xSP’s business is serving a multitude of companies (or tenants) such that each is configured separately and independently of one another. Each tenant represents a company and the xSP designates the ability to assign permissions using KEMP 360 Role Based Access Control (RBAC) only to a specific user or users within the applicable organization for ADC management purposes. Same benefits as the first example but the xSP will also decide how they want to monetize use of the ADC instances. Again, KEMP is flexible with how Central is deployed and used.
In closing, this blog post shows how flexible KEMP 360 Central is for enterprise and xSPs with many applications and load balancers no matter where they are located. Metered Licensing offers a pay-as-you-go consumption model whether you’re a large enterprise, small business or Service Provider.