WordPress.com use Amazon S3 for storing images, they do not serve images directly from Amazon, they use Varnish reverse proxy at front end, so not all images need to be served from S3, Varnish cache popular images and serve directly from its cache.
Many big web sites use varnish or squid at front end as reverse proxy.
We’re now using S3 as the primary storage for WordPress.com, rather than just for backups. We have some layers in front of it, notably Varnish, so the majority of our serving doesn’t hit S3. Still, our AWS bill went from around $200/mo to $1500/mo, and rising. It has simplified some of our requirements, but doesn’t look like it’ll save any money.
Tags: reverse proxy, scalability, squid, varnish
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Dec | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | 31 | ||||
One Response
Recent Links Tagged With "reverseproxy" - JabberTags
September 26th, 2008 at 2:34 am
1[...] public links >> reverseproxy Wordpress use Amazone S3 for storing images Saved by ridwandhk on Wed 24-9-2008 Make your own cheap charlie CDN Saved by jyaire on Sun [...]
RSS feed for comments on this post · TrackBack URI
Leave a reply