Home » Technologies » Ruby on Rails and Amazon

•  Quick Application Building. Using RoR can cut the build time from five or ten days down to a day. In fact, many Ruby on Rails applications only take several minutes to build.
•  Speed. Because RoR is easy and simple, developer productivity is enhanced by the swift feedback loop.
•  Simplicity. The Rails framework is impressively intuitive due to the fact that it is mostly database-oriented.
•  Popularity. There are a numerous sites that use Ruby on Rails at this point, and there are even search engines built with rails, such as ChaCha, advertised as the first human-powered search engine.

• Minimal effort. Amazon EC2’s simple web service interface allows you to obtain and configure capacity withlittle effort. It provides you with complete control of your computing resources and lets you run on Amazon’s proven computing environment. 
• Time savings. Amazon EC2 reduces the time required to obtain and boot new server instances to minutes, allowing you to quickly scale capacity, both up and down, as your computing requirements change. Amazon EC2 provides developers the tools to build failure resilient applications and isolate themselves from common failure scenarios.
• Pay as you go. Amazon EC2 changes the economics of computing by allowing you to pay only for capacity that you actually use. No need to plan ahead of how much computing power you will need, just build the infrastructure that can grow. 

• Scalable. Amazon S3 can scale in terms of storage, request rate, and users to support an unlimited number of web-scale applications. It uses scale as an advantage: Adding nodes to the system increases, not decreases, its availability, speed, throughput, capacity, and robustness. 
• Reliable. Store data durably, with 99.99% availability. There can be no single points of failure. All failures must be tolerated or repaired by the system without any downtime. 
• Fast. Amazon S3 must be fast enough to support high-performance applications. Server-side latency must be insignificant relative to Internet latency. Any performance bottlenecks can be fixed by simply adding nodes to the system. 
• Inexpensive. Amazon S3 is built from inexpensive commodity hardware components. As a result, frequent node failure is the norm and must not affect the overall system. It must be hardware-agnostic, so that savings can be captured as Amazon continues to drive down infrastructure costs. 
• Simple. Building highly scalable, reliable, fast, and inexpensive storage is difficult. Doing so in a way that makes it easy to use for any application anywhere is more difficult. Amazon S3 must do both.