Support and Docs

3 Topics
Last post 11 November 2014 By Nadja Kristiansen
1 Topics
Last post 20 March 2014 By Carsten E. Madsen
0 Topics
Last post N/A By N/A
0 Topics
Last post N/A By N/A
1 Topics
Last post 02 April 2014 By Carsten E. Madsen

eSeller Cloud Content Delivery Network

  • 07/01/2015

eSeller Cloud employs a global Content Delivery Network (CDN) to ensure that shops respond fast even in remote geographic locations and that eSeller Cloud is able to scale to many concurrent visitors. CDN makes your shop up to 10x faster compared to the same shop without CDN.

A CDN is a geographically distributed network of cache servers. Whenever a visitor visits a shop, the data is passed through the Cache server which is geographically closest to the user. For the sake of example, let’s say that a visitor in Berlin visits a specific product page. The request for the product page is sent from the user to the closest Cache server which in this case is probably in Frankfurt. The Cache server in Frankfurt does not have a copy of the requested page so it requests the page from the eSeller Cloud servers, it then saves the page and forwards it to the visitor. The cache server stores the page for a period of time and if another user in the vicinity visits the same page, the cache server can send the page directly to this new customer without even contacting the eSeller Cloud servers. – Obviously this process is entirely transparent to the visitors, - the only difference they experience is that pages are fast.

The CloudFront CDN used by eSeller Cloud has cache servers in the following geographic locations:

United States

  • Atlanta, GA
  • Ashburn, VA (3)
  • Dallas/Fort Worth, TX (2)
  • Hayward, CA
  • Jacksonville, FL
  • Los Angeles, CA (2)
  • Miami, FL
  • New York, NY (3)
  • Newark, NJ
  • Palo Alto, CA
  • San Jose, CA
  • Seattle, WA
  • South Bend, IN
  • St. Louis, MO


  • Amsterdam, The Netherlands (2)
  • Dublin, Ireland
  • Frankfurt, Germany (3)
  • London, England (3)
  • Madrid, Spain
  • Marseille, France
  • Milan, Italy
  • Paris, France (2)
  • Stockholm, Sweden
  • Warsaw, Poland


  • Chennai, India
  • Hong Kong (2)
  • Mumbai, India
  • Manila, the Philippines
  • Osaka, Japan
  • Seoul, Korea
  • Singapore (2)
  • Taipei, Taiwan
  • Tokyo, Japan (2)


  • Melbourne, Australia
  • Sydney, Australia

South America

  • São Paulo, Brazil
  • Rio de Janeiro, Brazil

CDN Options

The regular eSeller Cloud CDN is limited to Europe only. – This means that overseas visitors may experience slower load times. Please contact customer services if you want to upgrade to the full global CDN.

Caching considerations when working with eSeller Cloud

Generally dynamic resources such as product information pages are cached for one hour but they are only cached for non-login customers with empty baskets and with empty favorite lists. As soon as a product is added to either basket or favorite list, dynamic resources are note cached. – This means that changes to prices, stock level and other dynamic properties for non-login customers with empty lists have a cache period of 1 hour.

Static resources such as images, CSS and javascript is cached for a variable amount of time, up to 6 hours.

Changes to stock level and other dynamic properties may take up to one hour to propagate for non-login customers with empty baskets. Adding a product with a cached non-positive stocklevel to basket will result in a warning to the visitor that the product is not in stock and the product won’t be added to basket. Note that stock level and other dynamic properties may also be cached by the webserver (cache will not be invalidated by adding to basket).

Changes to CSS and JS files may take several hours to propagate.
– Ensure that IsJsCssVersionInQueryParmEnabled (under shop >> all settings) is enabled or if handling css and js manually, - add version numbers to filename as per normal best practice.

When making design changes it is sometimes necessary force load an uncached version of a resource.
– Adding a unique parameter to the URL will force the CDN to serve a fresh version of the resource.

When adding or changing a domain name it is important that you contact Customer Services to ensure that the CDN configuration reflects the changes.