This week, the Apache Software Foundation Board promoted Traffic Server to a top-level project (TLP). This is a big step going forward, as it recognizes Traffic Server as an active and well-functioning open-source community. There is nothing to stop us now!
Traffic Server is a fast, scalable, and extensible HTTP/1.1-compliant caching proxy server, which Yahoo! donated to the Apache Foundation. Since incubation inception last July, six new committers joined the project and the v2.0.0-alpha version was released. Some 170 Jira bug tickets have been resolved so far, and numerous new bugs and enhancement requests have been filed.
The final 2.0.0 release is almost ready, and should be available soon. The v2.0.x releases are all very close to the same code Yahoo! has successfully been using internally for years. It's fair to say that it is well tested.
In addition to the stable 2.0.x releases, we have a new developer-only release about to hit the download servers. We have adopted the HTTPD (and formerly, Linux) notion of even major release numbers for production releases and odd numbers for developer releases. So the next release after v2.0.0 will be v2.1.0. We hope to achieve a v2.2.0-beta release sometime this summer.
So let's talk more about what has happened during our incubation period, particularly related to the code. There has been a lot of clean-up and a number of significant improvements:
- The trunk is now 64-bit compatible. Not only can this speed up the server, but it also allows much more RAM to be allocated to the caches and allow us to handle more connections.
- Portability - the 2.0.x releases should build on most common Linux flavors. The upcoming 2.1.0 release also builds on many more UNIX platforms, such as Solaris, FreeBSD, and MacOSX.
- Small performance and latency related improvements were made in the 2.0.x releases. The 2.1.x development release promises even better performance: We've seen 2x or greater improvements, hitting well over 75,000 requests/second on a single box.
- Large disk support is ready and will be available in the next (2.1.x) release. This allows up to 0.5PB disk partitions for cache.
- There were many documentation updates. We even have a new home page that looks awesome (our product manager made me say that).
There is a lot of development activity in the community right now, which promises more features, capabilities, and performance in several important areas:
- Cache improvements not only give us support for vastly larger caches, they also noticeably improve performance and reduce latency.
- New additions to APIs include more scalable statistics, easier fetches of HTTP pages, and other important changes to enable new, exciting plugins to be developed.
- Significant work has been done to make it easy to use and deploy Traffic Server in cloud environments. For instance, there is a Amazon EC2 AMI available.
- Continuous improvements were made in portability, ease of use, and code cleanup. One goal is to make the code base smaller, and therefore easier to work with.
In the coming months, look for some plugins to be released, further extending Traffic Server's capabilities (and showing how extensible the server can be). The community is thriving, and we have a lot of fun, so come visit us in IRC, mailing lists, and community blogs. Things will change a bit now after graduation. So make sure you check out our new home page as we make the transition from a podling to a TLP.
This post was contributed by Leif Hedstrom and Miles Libbey,
Yahoo! Traffic Server