Loading ...
close

Would you like to discuss your environment with a knowledgable engineer?

Preferred communication *

Thank you. We will be in touch with you shortly

Articles & Blog

  • aiScaler Enables Acceleration Of Sites Requiring Registration And Log

    Posted by on October 25th, 2010

    aiCache allows you to cache a site’s content and enforce the registration/login policy. Users that are not logged in or registered, will not be allowed to view cached content and will be subject to normal handling; i.e. “asked to register and sign in to view the content.” Let take an example news website “www.acmetimes.com”. The […]

    read more
  • aiScaler for no-overhead error reporting

    Posted by on October 25th, 2010

    You might need a method to allow reporting of assorted error conditions. For example, your web site might offer videos, breaking news and other APIs that are invoked by AJAX or some other form of client-side Javascript. When these APIs fail to respond, you would like to have some way to report the error condition […]

    read more
  • aiScaler scales advertiser supported sites with pre-fetch technology

    Posted by on October 25th, 2010

    Websites depend on ads served by third party consolidators to generate revenue.  These consolidators API’s to enable the correct advertisement to be shown and analytics collected.  These API’s support multiple customer sites and are subject to wide variations in performance.  Site using these services suffer under heavy traffic conditions based on poor response time from […]

    read more
  • aiScaler Mobile Client Caching Support

    Posted by on October 25th, 2010

    aiCache uses the hostname and URL of request  as a signature of  cached responses. Some sites require different cacheable content in response to requests for the same URLs, depending on a value of a User Agent HTTP header present in the request.  User Agent HTTP header identifies browser’s make and model. A site serving mobile […]

    read more
  • User Agent based caching

    Posted by on October 25th, 2010

    aiCache now has the capability to add User Agent string to signature of cacheable responses. By default, Aicache uses hostname  and URL of request, possibly sanitized by removing some parameters or discarding the complete query string, as a signature of (pointer to) cached responses. Some sites might serve different cacheable content in response to requests for […]

    read more
  • Troubleshooting 101 with aiScaler

    Posted by on October 25th, 2010

    You’re in charge of a complex web site with a multitude of sub-domains, hosting all kind of information: editorial news, search, viewer comments, videos, news feeds, financial stock quotes. It is a thing of beauty, with 20+ APIs of all sorts, few dozen web, application and database servers – all working in concert to drive […]

    read more
  • Clustering aiScaler: United We Stand …

    Posted by on October 25th, 2010

    Most web site deploy aiCache in multiples, for a number of reasons. Even if your site’s traffic doesn’t warrant multiple Aicache servers, you’re still advised to have at least two, so that one can go down or be taken down for maintenance, without affecting the site. With more than one aiScaler server deployed, it makes […]

    read more
  • Configuring Client-to-Origin Server Persistence.

    Posted by on October 25th, 2010

    Some sites have a need to “pin” clients to specific origin servers. For example, a client A might need to be pinned to origin server 1, client B to origin server 2, while client C might be served by any available origin server. The reasons for such configuration may vary but a common theme to […]

    read more
  • Front-ending with aiScaler, the additional benefits.

    Posted by on October 25th, 2010

    With aiCache front-ending client requests – receiving and processing them before they ever get to your origin web server, Aicache is capable of providing even more benefits. Enforcing time, size and sanity limits on requests. Due to extremely efficient,  non-blocking multiplexed IO model of aiScaler, it is ideally suited to front-end user traffic , while […]

    read more
  • Stayin’ alive…

    Posted by on October 25th, 2010

    An all too common web site failure is overwhelming (running out of space on) log partition. It can happen due to a failure to rotate and offload log files, unexpected spike in traffic and similar conditions. A normal reaction to such out-of-space condition is  for web server to abort serving requests (exit) and hope that […]

    read more
US 1 (408) 744-6078   EU +44 20 7993 4587