Hi there, I'm trying to evaluate if Django might be fit for a project I'm going to be working on. The main requirement is to be bulletproof in regards to availability even in very high volume.
I assume a setup of a few web/app servers and one or more database servers and a load balancer (software). Caching is good if your data doesn't need to reflect real time state of the database. The application in question will require real time access all the time, so caching might not be used. I understand that Django uses the share-nothing approach, but: 1. What happens when an app server crashes? What happens to the users on it? Are they forced to log in again? is their session lost? 2. How are the sessions stored? Is it RAM? disk? DB perhaps? Does anyone have more information in regards to the actual setup recommended for clustered enviroments? I've looked around but haven't found answers to these 2 questions. Thanks, Harel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
