Home > Partners > aiCache

aiCache

logo-Alfresco-v1.png http://aicache.com/
Web Application Acceleration

Summary Statement

aiCache reduces the time to deliver content, scales the number of requests per second (RPS) your site is capable os sustaining by a level of magnitude, while providing real-time reporting on the performance of your site. 

Features

  • 250,000 HTTPS RPS (requests per second)
  • HTTPS support with 2Gbps of raw AES256 bulk encryption throughput and 15,000 RSA-1024 sessions per second on common 64bit hardware.
  • Pattern matching and TTL's give precise control of the cache configuration.
  • Document freshness controls including cookie- driven and on-demand header-driven cache expiration.
  • Execute customer-specific code the edge.
  • Highly Available, cluster aware with VIP support.

Diagnostics & Monitoring

CLI, web and SNMP interface
Monitors and reports health of origin servers

Mobile Support

Identifies mobile devices and serves the correct content based on capabilities of device.
Prefetch feature accelerates mobile ad-serving of non-cacheable responses

Protection & Security

DOS (Denial of Service) and DDOS (Distributed Denial of Service) protection including reverse-turing and access tokens
Admin fallback feature keeps site operational during a catastrophic failure.

ServerTemplate Summary

ServerTemplates published by RightScale Partners can be found in the MultiCloud Marketplace.  Go to Design -> MultiCloud Marketplace -> ServerTemplates.  Use the filter options to find correct ServerTemplate(s).   In order to use the ServerTemplate, you must first import it to your local view.

Some Partner ServerTemplates are not designed to launch server instances.  In some cases, the purpose of a ServerTemplate is to provide access to a collection of RightScripts. 

TYPE
NAME
DESCRIPTION
ServerTemplate AiCache6 Installs and configures version 6 of the aiCache Web Application Accelerator on an EC2 instance.  Additionally, the scripts within the ServerTemplate will tune kernel parameters on the instance to take full advantage of aiCache's capabilities.  View the ServerTemplate's description for more detailed information.

 

The ServerTemplate has numerous inputs that are used to configure the instance when it's launched.  Many of these inputs have default values that can be modified, if desired.  The following inputs are required and must be set with explicit values:

INPUT DESCRIPTION
AICACHE_VERSION Set this to "ignore" via the pulldown menu to use the latest version.  If you know that you want to use a specific previous version, enter the value (e.g. 6109) in the text box.
AIC_CFG_BUCKET The name of the S3 bucket which contains your configuration file.
AIC_CFG_FILE The name of the configuration file within the AIC_CFG_BUCKET.  To get started, you can download a base configuration file from http://rightscale.aicache.com/template.cfg and make the modifications described in the Documentation section below.
AIC_LOGGING_DEST_PATH The location on the server where the archived aiCache log files should be stored.  Select the /mnt/logs option from the pulldown menu or check the "override dropdown" box at the right to enter a different path.
PRIVATE_SSH_KEY The SSH key to allow the aiCache server to access other servers in the deployment.

Documentation

Once aiCache is installed, there are a few basic settings that need to be configured. The configuration file (/root/default.cfg) contains numerous settings that can be modified to alter the behavior of aiCache, but the essential ones are:

/@api/deki/files/4508/=config_file_aicache_example.txt

website                      # Section header
hostname   aicache.com       # Main host name
cname      www.aicache.com   # Alternative name (exact match)
wildcard   amazonaws.com     # Process all requests made to *amazonaws.com

For sites that can not be matched to any hostname, CNAME, or wildcard values in the configuration file, aiCache returns the error "409 Website not found."

Next, you'll need to set the caching rules.  Effectively, you tell aiCache that when a request's URL matches a string, then the response should be cached for a certain amount of time. The match can be exact, partial, or regular expression-based.  Here are a few quick examples:

pattern \.php regexp 1m       # cache for 1 minute, cache dynamic files with caution
pattern .css simple 7d no_log # cache for a week, do not log in acces log file

Lastly, you'll need to set the "origin servers" for your setup.   Origin servers are the primary application servers that aiCache will accelerate. You must add at least one origin.

origin 1.2.3.4 80  # Replace with your server's IP.  "80" is the port number.
You must to post a comment.
Last Modified
23:38, 16 May 2013

Tags


Announcements

None

Glossary | 用語용어 Site Map | Site Help Community Corporate Site Get Support Dashboard Login
Doc Feedback Product Feedback Resources MultiCloud Marketplace Forums

Dashboard Status


© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.