Jump to content

Apache Traffic Server

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by LE666 (talk | contribs) at 22:18, 29 February 2016 (remove wrong logo (it's not the Apache Traffic Server logo)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Apache Traffic Server
Developer(s)Apache Software Foundation
Stable release
6.1.1 / 8 February 2016; 8 years ago (2016-02-08) [1]
Repository
Written inC++
Operating systemCross-platform
Available inEnglish
TypeWeb cache, Proxy server
LicenseApache License 2.0[2]
Websitetrafficserver.apache.org

The Apache Traffic Server (ATS) is a modular, high-performance reverse proxy and forward proxy server, generally comparable to Nginx and Squid. It was created by Inktomi, and distributed as a commercial product called the Inktomi Traffic Server, before Inktomi was acquired by Yahoo!.

Shortly after Yahoo! released the TS source to Apache as an Apache Incubator project in July 2009,[3] a guest editor on Yahoo!'s online publication OStatic [4] stated that Yahoo! uses TS in production to serve more than 30 billion objects per day on sites like the Yahoo! homepage, and Yahoo! Sports, Mail and Finance.

On April 21, 2010, the Apache board accepted Traffic Server as a TLP, graduating the project out of incubation.[5]

Current version

As of February 2016, ATS is in version 6.1.1, with quarterly minor versions scheduled. Beginning with version 4.0, all releases are considered stable for production, and follow regular semantic versioning. No more developer preview releases will be made, instead, the Git master branch is considered preview quality at all times. Long term support is provided for the last minor version within a major release, for one added year.[6]

ATS has, as of v6.0.0, good support for the next generation HTTP protocol, HTTP/2 (aka H2). On the Is TLS Fast Yet site, it scores 100%. ATS is actively developed and supported by several large companies, as well as many individual contributors.

Features and performance

The OStatic post describes TS as shipping "... with not only an HTTP web proxy and caching solution, but also ... a server framework, with which you can build very fast servers for other protocols". Traffic Server has been benchmarked to handle 200,000 requests per second or more (small objects out of cache).[7] At a talk at the 2009 Cloud Computing Expo,[8] members of the Yahoo! TS team stated that TS is used in production at Yahoo! to handle 400TB of traffic per day using only 150 commodity machines. The OStatic post describes TS as the "product of literally hundreds of developer-years".

Deployment

In the context of cloud computing, TS would sit conceptually at the edge of the cloud, routing requests as they come in. In Yahoo!, it is used for the edge services as shown in a graphic[9] distributed at the 2009 Cloud Computing Expo depicting Yahoo!'s private cloud architecture. In practical terms, a typical server configuration might use TS to serve static content, such as images and JavaScript, Cascading Style Sheets (CSS), and HyperText Markup Language (HTML) files, and route requests for dynamic content to a web server such as Apache HTTP Server.

References

  1. ^ "PGP signature". https://trafficserver.apache.org/. Apache Software Foundation. 2015-12-16. Retrieved Jan 5, 2015. {{cite web}}: External link in |website= (help)
  2. ^ "Traffic Server license file". Apache Software Foundation. Retrieved 2009-12-24.
  3. ^ "Apache Incubator Wiki August 2009 Board reports". 2009-08-12.
  4. ^ "Yahoo's Cloud Team Open Sources Traffic Server". 2009-11-02.
  5. ^ "Traffic Server graduates to top-level open-source project". 2010-04-23.
  6. ^ "Official project release management process". 2013-09-06.
  7. ^ "The Apache Software Foundation Announces Apache Traffic Server v3.0.0 : The Apache Software Foundation Blog". 2011-06-14.
  8. ^ "2009 Cloud Computing Expo". 2009-08-12.
  9. ^ "Yahoo's edge services graphic". 2011-06-14. Retrieved 2011-06-14.