#WIKIMEDIA MEDIAWIKI HOW TO#

The backend caches scale horizontally and have a logical capacity equal to the total of all servers. Contrary to the frontends, these are routed by a consistent hash, and they also persist their cache on disk (instead of in memory). Backend caching: The backend HTTP caches are routed to by frontend caches in case of a cache miss.Each frontend cache server likely holds the same set of responses in its cache, the logical capicity for the frontend cache is therefore equal to 1 server's RAM. The LVS load balancers route the request to a random cache proxy server to maximise the amount of parallel traffic we can handle. Frontend caching: This is an in-memory HTTP cache (uses Varnish, called 'Varnish frontend', or varnish-fe).TLS termination and HTTP/2 handling, handled by HAProxy.Each cache server hosts all three of these layers. The caching servers are implemented as a reverse proxy consisting of three layers: TLS termination, frontend caching, backend caching.The public load balancers and caching proxies are located in all data centres (especially those with the sole role of being an edge cache, also known as 'pop'). Wikimedia Foundation owns its content-delivery network.» See also DNS, Global traffic routing, and LVS. The DNS resolves hostnames like en. ultimately points to an address like text-lb.*., for which the IP addresses are service IPs handled by LVS, which acts as a direct-routing load balancer to our caching proxies.

#WIKIMEDIA MEDIAWIKI HOW TO#

For how to use, install or contribute, see .Ī Wikipedia web request is processed in a series of steps outlined here (as of April 2020).For more about the history, see 'MediaWiki' on.This page documents its deployment at Wikimedia Foundation. MediaWiki is the collaborative editing software that runs Wikipedia.

Wikimedia mediawiki