Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to deploy a [Ruby on Rails] site in a scalable way?
    primarykey
    data
    text
    <p>I have been working on my [first] startup for a month now, and while it's probably atleast one more month away from an alpha release, I want to know how to deploy it the right way. The site will have an initial high amount of load (network + CPU) for a new user, so I am thinking of having a separate server/queue for this initial process, so that it doesn't slow down the site for existing users. </p> <p>Based on my research so far, I am currently leaning towards nginx + haproxy + unicorn/thin + memcached + mysql, and deploying on Linode. However, I have no prior experience in any of the above; hence I am hoping to tap the community's experience.</p> <ul> <li>Does the above architecture seem reasonable? Any suggestions/articles/books that you would recommend? </li> <li>Is Linode a good choice? Heroku/EY seem too expensive for me (atleast until I have enough revenue), but am I missing some other better option? MediaTemple?</li> <li>Any good suggestions on the load balancing architecture? I am still reading up on this. </li> <li>Is it better have 2 separate Rails server instances on 2 separate linodes, or running 1 instance on a linode of twice capacity (in terms of RAM/storage/bandwidth)? How many Linodes should I start with?</li> <li>Which Linux distribution should I choose? (Linode offers 8 different ones - <a href="http://www.linode.com/faq.cfm" rel="noreferrer">http://www.linode.com/faq.cfm</a>) Are there any relative advantages/disadvantages between them for a Rails site?</li> </ul> <p>I apologize if any of my questions are stupid or contradictory; please attribute it to my inexperience.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload