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! .
16-644: Shortly after Yahoo! released the TS source to Apache as an Apache Incubator project in July 2009, a guest editor on Yahoo!'s online publication OStatic 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. The latest stable version
32-435: A change contrary to the rules is required, such as restarting the freeze period. Common types of freezes are: In development environments using version control , the use of branching can alleviate delays in development caused by freezes. For example, a project may have a "stable" branch from which new versions of the software are released, and a separate "development" branch in which the developers add new code. The effect of
48-403: A long-term support period, the software developers impose a feature freeze : They make patches to correct software bugs and vulnerabilities , but do not introduce new features that may cause regression . The software maintainer either distributes patches individually, or packages them in maintenance releases , point releases , or service packs . At the conclusion of the support period,
64-424: 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). At a talk at the 2009 Cloud Computing Expo, 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
80-432: A specific LTS version in addition to a normal release cycle. Many projects, such as CentOS , provide a long period of support for every release. Feature freeze In software engineering , a freeze is a point in time in the development process after which the rules for making changes to the source code or related resources become more strict, or the period during which those rules are applied. A freeze helps move
96-414: A web server such as Apache HTTP Server . Long-term support Long-term support ( LTS ) is a product lifecycle management policy in which a stable release of computer software is maintained for a longer period of time than the standard edition. The term is typically reserved for open-source software , where it describes a software edition that is supported for months or years longer than
112-510: Is 9.2.2 and was released on August 3, 2023. The latest long-term support version is 8.1.8 and was released on August 3, 2023. As of June 2021, ATS is released in two stable versions, Version 8 is a long-term support version of ATS while version 9 is the latest stable release, 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,
128-466: Is called a regression . Two ways that a software publisher or maintainer can reduce the risk of regression are to release major updates less frequently, and to allow users to test an alternate, updated version of the software. LTS software applies these two risk-reduction strategies. The LTS edition of the software is published in parallel with the STS (short-term support) edition. Since major updates to
144-578: 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 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, JavaScript , Cascading Style Sheets (CSS), and HyperText Markup Language ( HTML ) files, and route requests for dynamic content to
160-642: 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. ATS has good support for the next generation HTTP protocol as of v6.0.0, HTTP/2 (a.k.a. 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. The OStatic post describes TS as shipping "... with not only an HTTP web proxy and caching solution, but also ...
176-401: The software development process and software release life cycle . Long-term support extends the period of software maintenance ; it also alters the type and frequency of software updates ( patches ) to reduce the risk , expense, and disruption of software deployment , while promoting the dependability of the software. It does not necessarily imply technical support . At the beginning of
SECTION 10
#1733085706403192-476: The STS edition are published more frequently, it offers LTS users a preview of changes that might be incorporated into the LTS edition when those changes are judged to be of sufficient quality . While using older versions of software may avoid the risks associated with upgrading, it may introduce the risk of losing support for the old software. Long-term support addresses this by assuring users and administrators that
208-409: The product either reaches end-of-life , or receives a reduced level of support for a period of time (e.g., high-priority security patches only). Before upgrading software, a decision-maker might consider the risk and cost of the upgrade. As software developers add new features and fix software bugs, they may introduce new bugs or break old functionality. When such a flaw occurs in software, it
224-448: The project forward towards a release or the end of an iteration by reducing the scale or frequency of changes, and may be used to help meet a roadmap . The exact rules depend on the type of freeze and the particular development process in use; for example, they may include only allowing changes which fix bugs , or allowing changes only after thorough review by other members of the development team. They may also specify what happens if
240-465: The software will be maintained for a specific period of time, and that updates selected for publication will carry a significantly reduced risk of regression. The maintainers of LTS software only publish updates that either have low IT risk or that reduce IT risk (such as security patches ). Patches for LTS software are published with the understanding that installing them is less risky than not installing them. This table only lists software that have
256-411: The software's standard edition. Short-term support (STS) is a term that distinguishes the support policy for the software's standard edition. STS software has a comparatively short life cycle, and may be afforded new features that are omitted from the LTS edition to avoid potentially compromising the stability or compatibility of the LTS release. LTS applies the tenets of reliability engineering to
#402597