Traffic Server

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Apache Traffic Server
ASF-logo.svg
Developer(s) Apache Software Foundation
Stable release 4.2.1.1 / 23 July 2014; 35 days ago (2014-07-23) [1]
Written in C++
Available in English
Type Web server
License Apache License 2.0[2]
Website trafficserver.apache.org

The Apache Traffic Server (TS) 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!. Yahoo!'s OStatic guest post Yahoo's Cloud Team Open Sources Traffic Server[3] states 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. Yahoo! released the TS source to Apache as an Apache Incubator project in July 2009.[4] On April 21, 2010, the Apache board accepted Traffic Server as a TLP, graduating the project out of incubation.[5]

TS is now in version 4.0.1, with quarterly minor versions scheduled. As of version 4.0, all releases are considered stable release, and all releases follow regular Semantic Versioning. No more developer preview releases will be made, instead, the git master branch is considered preview quality at all time. Long term support is provided for the last minor version within a major release, for one additional year.[6]

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".

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, CSS, and HTML files, and route requests for dynamic content to a web server such as Apache HTTP Server.

References[edit]

External links[edit]