🆚 Apache Traffic Server vs. Heroku Vegur

Compare technologies based on real-world usage data *

Type

Caching solution
Load balancer

About

Apache Traffic Server is a fast, scalable, and extensible web proxy cache that improves performance by caching frequently accessed information at the edge of the network.

Heroku Vegur is open-source proxy and load balancing software.

Headquarters

Wilmington, Delaware, United States
San Francisco, California, United States

Website

Pricing

Free ✔️Open source
Free ✔️Open source

Categories

Caching › Rank #19
Load Balancers › Rank #12
Load Balancers › Rank #10

Popularity

Determined by the number of sites using each technology.

The Heroku Vegur load balancer is 1.7 times more popular than Apache Traffic Server.
Total websites

Market share

Load Balancers

Popularity by country

Determined by the number of sites detected from each country.

Heroku Vegur is more popular in the United States, the United Kingdom, and Germany, while Apache Traffic Server is more popular in the Czech Republic, Slovakia, and China.
Czech Republic
United States
United Kingdom
Germany
Australia
France
Brazil
Japan
Canada
Slovakia

Awards

Popularity by domain category

Determined by the number of sites in each category.

Heroku Vegur is more popular among sites focused on business, marketing and merchandising, and education and reference, while Apache Traffic Server is more commonly used on public information and portal sites sites.
Business
Marketing/Merchandising
Education/Reference
Entertainment
Internet Services
Blogs/Wiki
Online Shopping
Travel
Software/Hardware
Non-Profit/Advocacy/NGO

Top sites

Top-ranked sites that use these technologies.

Name
Rank
#495
View more ➝
Name
Rank
#3,593
View more ➝

See also

* According to recent studies, many of online reviews are fake.
When making your decision, it is better to rely on data that cannot be falsified.
Our service evaluates the popularity of technologies by the number of websites using them.

Statistics were last calculated on .
For details, see our methodology and disclaimer.