Maybe so, but yes, it would be good to clarify. I've used a t1.micro for 
the project in question anyway, for the price it's no huge overhead (and we 
can easily remove it later).

Richard.


On Thursday, 3 January 2013 15:26:40 UTC, Srini wrote:
>
> On second thought: the LAMP role is probably meant to be used that way. 
> Probably DNS round robin with a low latency ?
>
> Hopefully someone from scalr will confirm. 
> Srini
> Sent on my BlackBerry® from Vodafone
> ------------------------------
> *From: * RichBos <[email protected] <javascript:>> 
> *Date: *Thu, 3 Jan 2013 07:20:43 -0800 (PST)
> *To: *<[email protected] <javascript:>>
> *Cc: *<[email protected] <javascript:>>
> *Subject: *Re: Nginx balancer required for x2 LAMP farm?
>
> Thank you Srini, and yes, that would be as I suspected, it was the 
> advisory to the contrary in the Scalr wiki which sent me off track.
>
> But you never know, there may have been some Nginx Scalr magic baked into 
> the LAMP roles I was unaware of, it's usually best just to ask the question.
>
> Richard
>
>
>
> On Thursday, 3 January 2013 15:10:28 UTC, Srini wrote:
>>
>> Nginx or another load balancer would be needed. 
>>
>> Srini
>> Sent on my BlackBerry® from Vodafone
>> ------------------------------
>> *From: * RichBos <[email protected]> 
>> *Sender: * [email protected] 
>> *Date: *Thu, 3 Jan 2013 06:54:23 -0800 (PST)
>> *To: *<[email protected]>
>> *ReplyTo: * [email protected] 
>> *Subject: *Nginx balancer required for x2 LAMP farm?
>>
>> Hi, I'm just wondering if an Nginx load balancer is required for a x2 
>> role LAMP Farm? (As it would be using x2 App instances). I would expect so 
>> but the Wiki documentation says no. However as I understand it wouldn't the 
>> DNS be better pointed at the Nginx LB rather than the LAMP (app) 'role'? 
>> I'm only thinking so as if not how would (web/app) traffic be distributed 
>> evenly between the x2 LAMP instances? Or have I misunderstood things?
>>
>> http://wiki.scalr.com/display/docs/Mixed+images+-+LAMP
>>
>> Any advice appreciated.
>>
>> Richard.
>>
>> -- 
>>  
>>  
>>
>

-- 


Reply via email to