High Performance Scaling Expert
Some problems are easy to solve
peak periods and scalability
minimal round-trip latency
protects frontend from
maintenance windows and
varnish takes the load,
without breaking a sweat
dampening attack on appservers
detect-and-redirect or simply serve a different site
realtime http-level control and transparency
simplify multi-domain site routing,
rewrites and redirects
(for modern architectures)
written for 64-bit OS
shared-nothing work delegation
** per second**
request must be delivered
with minimal effort
shared memory log and
Varnish Configuration Language
powerful yet simple
Deploy 2 or more Varnish servers
for high availability
what do you need to do?
3 working days
recommended scenario #1: varnish as load balancer
We need these things before deployment:
frontend domain names
backend hostnames, ip, port numbers
DNS / load balancer config
host(s) to deploy Varnish on
what to do, when, how. next step?
installation and configuration
Varnish installed on hosts.
Initial VCL set up.
preprod Quality Assurance.
spillover from day 3
Access to highly qualified Varnish consultants.
What mobile device is connected?
for developers and system administrators
Real-time aggregated stats from varnish cluster
Here are some examples of the type of statistics you may track:
and you will sleep better at night
at the end plz