Application delivery controller
 | This article needs additional citations for verification. (May 2007) |
An application delivery controller (ADC) is a computer network device in a datacenter, often part of an application delivery network (ADN), that helps perform common tasks, such as those done by web accelerators to remove load from the web servers themselves. Many also provide load balancing. ADCs are often placed in the DMZ, between the outer firewall or router and a web farm.[citation needed]
Features
A common misconception is that an Application Delivery Controller (ADC) is an advanced load-balancer.[citation needed] This is not an adequate description.[opinion]
An ADC is a network device that helps applications direct user traffic in order to remove the excess load from two or more servers. In fact, an ADC includes many OSI layer 3-7 services, which happen to include load-balancing. Other features commonly found in most ADCs include IP Traffic Optimization, Traffic Chaining/Steering, SSL offload, Web Application Firewall, CGNAT, DNS, and proxy/reverse proxy, among others. They also tend to offer more advanced features such as content redirection as well as server health monitoring. In the context of Telco Infrastructure, ADC could provide services for Gi-LAN area.[citation needed]
History
Starting around 2004, first generation ADCs offered simple application acceleration and load balancing.[citation needed]
In 2006, ADCs began to mature when they began featuring advanced applications services such as compression, caching, connection multiplexing, traffic shaping, application layer security, SSL offload, and content switching, combined with services like server load balancing in an integrated services framework that optimized and secured business critical application flows.[citation needed]
By 2007, application acceleration products were available from many companies.[1]
Until leaving the market in 2012, Cisco Systems offered application delivery controllers. Market leaders like F5 Networks, Radware, and Citrix had been gaining market share from Cisco in previous years.[2]
The ADC market segment became fragmented into two general areas: 1) general network optimization; and 2) application/framework specific optimization. Both types of devices improve performance, but the latter is usually more aware of optimization strategies that work best with a particular application framework, focusing on ASP.NET or AJAX applications, for example.[3][4]
See also
References
- ^ Bednarz, Ann (2007-07-03). "Gear makers bundle network optimization features". Network World. Retrieved 2013-05-26.
- ^ Burt, Jeffrey (2012-09-20). "Cisco Ending ADC Business, Ceding Market to F5, Citrix, Riverbed –". eweek.com. Retrieved 2013-06-27.
- ^ Kerner, Sean Michael (2008-05-01). "Applications And Networks Need to Unite". InternetNews.com. Archived from the original on 2008-05-05. Retrieved 2013-05-26.
- ^ Edgenexus Limited (2022). Edgenexus load balancers and Application. Retrieved from https://www.edgenexus.io/.
- Articles with short description
- Short description with empty Wikidata description
- Articles needing additional references from May 2007
- All articles needing additional references
- All articles with unsourced statements
- Articles with unsourced statements from April 2022
- Articles with unsourced statements from May 2017
- All articles with minor POV problems
- Articles with minor POV problems from April 2022
- Networking hardware
- Load balancing (computing)