This document discusses strategies for scaling large Rails applications. It notes that while tutorials are helpful for getting started, apps often grow larger and require scaling to reduce costs, headaches, and other issues. The document recommends separating an app across different servers based on functions like static files, business logic, authentication, and data storage. It suggests using JSON for communication between servers due to its support in Ruby and ability to create APIs.

1. Building Large Rails App
Karthikeyan A K
Fired Recently
mindaslab@gmail.com

2. rails new <app_name>
● Tutorials just get you started
● Apps grow
● Scaling
– Cost
– Headhache
– Stupids

3. Scaling Easy?
● Heroku
– Cost
● Multiserver
– Headache
– It costs time

4. What App Has
● Client Data
● Business Logic
● Security
– Authentication
● File store
● Logging Stuff (for data-mining)

5. Separate it into servers
● CDN (static files)
● Bizlogic
● Login / Auth

6. Communication?

7. JSON
● Ruby's inbuilt support
● Can be converted to hash → Native Objects
● Can easily create API's out of it
– It is a API

10. Questions?