Skip to main content

Choosing a caching HTTP Proxy

Bryan Call (Yahoo!)
Average rating: ***..
(3.40, 5 ratings)
Slides:   1-PPTX 

HTTP Proxy Server and caches are becoming a vital part of any Web
engineers arsenal. Choosing the right intermediary for a particular problem
can be a difficult task. There is a lot of hype, FUD, and misconceptions out
there. Understanding what is important for your application is the key to
picking the right solution.

This presentation will introduce the audience to the common use cases of
HTTP proxy servers. We will discuss when you would use a particular
solution, and what is important from a technical perspective for each
problem. This includes

  • Efficient Server Load Balancing
  • Building reliable, redundant, and scalable HTTP applications
  • Implementing a CDN, or extending a commercial CDN
  • Doing forward and transparent proxy for e.g. a corporate firewall

We will examine some of the most common, and popular, free and Open Source
HTTP intermediaries, including (in alphabetic order):

  • Apache HTTPD with mod_proxy and mod_cache
  • Apache Traffic Server
  • Squid
  • Varnish
  • nginx

The analysis is a deep dive into capabilities, features, and of course
performance comparisons. We will show where certain applications are more
suitable for a particular problem, and where they are not. Applying our
knowledge of the server solutions with the understanding of the problem
space will give the audience a solid foundation to make the right decisions,
without having to roll the dices.

Photo of Bryan Call

Bryan Call


Bryan Call has been writing code and working with on large scale solutions for 14 years. He has experience optimizing and profiling projects, including Apache Traffic Server and many internal projects at Yahoo!.

He came to Yahoo! through an acquisition of a startup and has been working there for the last 12 years. He has worked on various products and teams, such as WebRing, GeoCities, People Search, Yahoo! Personal, Tiger Team (internal consulting team), Architect in the Platform Group, Architect in the Edge Platform, and now is working in the R&D Systems Group.

Bryan is also a commiter on the Apache Traffic Server project and instrumental in bring Traffic Server to the Apache Foundation.