Nuxeo Edge Cache allows you to cache binaries from your Nuxeo server on an Edge Cache server closer to your clients. It can act like a Content Delivery Network, to improve the speed of your downloads.
Nuxeo Edge Cache is composed by one Nuxeo addon to be installed on the Nuxeo server, and agents to be installed on a computer that will serve as the Edge Cache server. These agents are available with installers for Windows and OS X, or as a Docker image.
First install the Nuxeo Edge Cache addon, available from the Nuxeo Marketplace.
Nuxeo Edge Cache does not require any configuration on the Nuxeo server after its installation.
- Download and install the relevant agent for your system. They are available from the Marketplace Edge Cache page.
- Launch the Edge Cache agent and set it up.
- Windows: follow the instructions displayed.
- Linux: Use the command line (see the Command Line section below) to set up the Docker image.
- Debian 8.0 Jessie
- Ubuntu Xenial Xerus 16.04
- Windows Server 2016
The table below shows the available parameters.
||The port to bind|
||Activates SSL encryption on listening socket|
||The SSL Key to use|
||The SSL Certificate to use|
||30||The Time-To-Live for the Edge Cache server.
See the TTL section below
||The folder to use for cache storage|
||0||The size limit in Gb for this binding. 0 means unlimited.|
||The IPs to redirect to this Edge Cache Server.
See the IPs section below.
||The Nuxeo server to connect to|
||The Nuxeo administrator user|
||The Nuxeo administrator password|
||The hostname or IP to this Edge Cache server|
||The name of the connection|
||Unbinds a Nuxeo server from the Edge Cache server|
||The name of the Nuxeo server connection to unbind|
||Lists all the defined bindings|
When you connect to your Nuxeo server for download it will check the source IP that does the request. If the source IP belongs to a defined Nuxeo Edge Cache and this cache is alive, then it will redirect to it.
You can define the IP sources with the CIDR format:
188.8.131.52/24will map all the network
184.108.40.206will map just one IP
220.127.116.11/24;18.104.22.168/24will map those two networks
In the example, if three Edge Cache servers are defined on the same source, the closest definition will be evaluated first. If the source IP is
22.214.171.124 then the second proxy will be used first if it is alive, then will fallback to the second, etc.
The Time-To-Live is defined per Nuxeo server connection. It defines after how many seconds the Edge Cache server will be considered as offline.
The Edge Cache server will initiate a ping on the Nuxeo server every TTL - 2 seconds. For this reason the TTL cannot be inferior to 2 seconds.
Your Nuxeo server will redirect to your Edge Cache if the last ping from the Edge Cache server was received before the TTL expires. If not then it will send the binary itself and will not redirect to the Edge Cache for download, as it is considered dead.
A great addition to cloud deployments or for customers with multiple remote sites, Nuxeo Edge Cache removes the need to download the same file again and again at a given site when several users want to access the same content.
- The user requests a binary from the Nuxeo server.
- The Nuxeo server verifies if an Edge Cache server is registered on this IP.
- The Nuxeo server redirects to the Edge Cache server registered with this IP.
- The Edge Cache server receives the redirect request with the token.
- The Edge Cache server extracts the encryption key from the token.
- If the Edge Cache server has the binary stored and decrypted with the key, it is sent to the user. Else Edge Cache downloads the encrypted binary from the Nuxeo server and stores it while decrypting and sending it to the user.