Bad array indexing is considered deadly

[Laeeth Isharc via Digitalmars-d]

On Friday, 2 June 2017 at 10:37:09 UTC, aberba wrote:
> On Friday, 2 June 2017 at 02:11:34 UTC, Laeeth Isharc wrote:
>> On Wednesday, 31 May 2017 at 13:34:25 UTC, Steven 
>> Schveighoffer wrote:
>>> [...]
>>
>> Hi Steve.
>>
>> Had similar problems early on.  We used supervisord to 
>> automatically keep a pool of vibed applications running and 
>> put nginx in front as a load balancer. User session info 
>> stored in redis.  And a separate process for data 
>> communicating with web server over nanomsg.  Zeromq is more 
>> mature but I found sometimes socket could get into an 
>> inconsistent state if servers crashed midway, and nanomsg 
>> doesn't have this problem. So data update either succeeds or 
>> fails but no corruption if Web server crashes.
>>
>> Maybe better ways but it seems to be okay for us.
>>
>>
>> Laeeth
>
> How does that setup affect response time? Do you cache large 
> query results in redis?

Our world is very different from web world.  Very few users but 
incredibly high value.  If we have twenty users then for most 
things that's a lot.  We don't cache query results as it's fast 
enough and the data retrieval bit is not where the bottleneck is.


Laeeth