Hi Jonas, While I agree with all the points JP made, I still chose multiple processes in order to achieve greater security. I maintain information provided by my users that is sensitive. I have two apps, one that provides all of the front end (web) processing, and a second one that contains all the backend (non-web facing) processing. The only difference between the two is configuration: the backend app contains the private keys used to secure the data while the frontend app does not. If a vulnerability exists that exposes config (environment) variables to the web, then the private key simply would not be available as it does not exist in the front-end environment. I believe that this security enhancement is worth the negatives JP mentioned in his response. I'd like to hear from others if they have used this technique, or if they have an informed opinion on whether this technique has merit.
Cheers, Jack On Monday, April 15, 2013 10:57:52 PM UTC-7, Jonas Windey wrote: > > What are the benefits of putting multiple dyno's (ex. web and worker) on a > single app compared to putting each dyno on a separate app? > In terms of scalability, it would be the same since each dyno can be > scaled no matter how it's setup. > > The only real advantage I could see is that env variables are shared on > the same app, but that is something that can be overruled in the latter > setup too. > > The biggest advantage for the second setup is of course a free dyno/month > for each app. > > > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
