This scenario is a little bit more complex than Low usage (simplest scenario) but it provides some advantages:
Advantages | Disadvantages |
---|---|
Can be autoscaled. | Requires AWS EC2 instances |
Easier crash recovery | Requires manual configuration |
Very easy monitoring support (CloudWatch) | Requires AWS EBS. |
Requires some AWS know how. | |
Static files are not served from a cdn. |
This scenario is recommended if you want to rollout you application on AWS infrastructure. Usually it is non expensive to do this as it requires micro instances and low cost storage. For more information about AWS required components read:
This scenario can be easily optimized by using AWS S3 buckets for static files. This ensures faileover for static files and very easy horizontal scaling for sites. Below you can find the new diagram:
You can read more about AWS S3 storage on http://aws.amazon.com/s3/. In this version of fantastico there is no way to sync static module files with S3 buckets. This feature is going to be implemented in upcoming Fantastico features. As a workaround you can easily copy static folder content from each module on S3 using the tool provided from AWS Management Console.
You can see how to use AWS Management Console S3 tool on http://www.youtube.com/watch?v=1qrjFb0ZTm8
It is usually a good idea to change the number of parallel connections supported by your linux kernel: