We just published the 2016 Magic Quadrant for Application Delivery Controllers (ADC), a market which many folks still refer to as load-balancers. We evaluate 11 vendors that meet inclusion criteria including A10, Amazon Web Services, Barracuda, Brocade, Citrix, F5, KEMP, Microsoft, NGINX Inc., Radware, and Sangfor.
I’ll cut straight to the chase: …the market is in a state of flux, with a growing divergence between the needs of traditional I&O and application-centric personnel…
For example, a common scenario we observe within our clients is that developers prefer open-source or their cloud providers’ embedded offering, but the corporate IT standard is a more established traditional player like F5 or Citrix. Consequently, each group goes off and does their own thing.
Thus, this Magic Quadrant covers mainstays like F5, Citrix, Radware and A10, but also the likes of AWS, Microsoft (Azure) and NGINX, Inc. This reflects the emerging user preferences for lightweight, low/no-cost, low-friction access for application-led and developer-centric initiatives…load-balancers are cool again. In fact, there are now four vendors (out of 11) in the Magic Quadrant without a flagship hardware form-factor product (Amazon, Brocade, Microsoft and NGINX) whereas just 3 years ago there was only 1 (Riverbed). Here’s the link: Magic Quadrant for Application Delivery Controllers.
This year, we also published an inaugural Critical Capabilities for ADCs as a companion to the Magic Quadrant. In it, we dive into the most common enterprise use-cases and evaluate the vendors against them. The specific usage scenarios involve using ADCs for: basic load balancing, standard enterprise apps, highly customized enterprise apps, Midmarket environments, and developer-led app initiatives.