Will Panda on database file persistance

Hey there,


Thanks for getting back to me so quickly!  With regards to your question, it would be much better to store your files in the DB rather than having them stored on the individual instance.  The problem is if they're stored directly onto one single session and instance, a user might hit another instance when returning for a following request.  It is a much better practice to have everything loaded onto the DB, so that all the instances can access that information, and the user will be able to get to the files regardless of the app instance they hit.

Doing it any other way will cause a lot of problems when you try and scale up.  There are additional problems if you are routing all requests to one single instance since you might overload it with users all trying to hit the same instance simultaneously.

-Will

On Wed, Feb 6, 2013 at 7:54 AM, <fuckyourdaddy@numerica.cl> wrote:
Hi Will,

Indeed, there is an architectural doubt I would like to share with you people.
I succesfully deployed my app on one server and then on two and that opened my eyes
into that normal load balancing won't suffice for me because what my app does is
file treatment in a tmp directory (which I then clean).
The trouble is, since files will live in the directory that the instance which first serves the request will provision,
I need subsequent requests from the same client to be server by the same instance, or else files will not be available.
I think this is called a sticky session (not sure). So, in short, my question is does EY support such type of load balancing?
Any kind of recommendations or comments on this structure is also welcome.
However, I'm pretty sure putting those files into the database would not be a good idea, would it?
By the way, don't you have a forum? I'd be better off asking this openly.

Salutations
Numerico. S.C.L.

On 04.02.2013 17:41, Will Adams wrote:
Hi numerico,

Hope all is going well with your Engine Yard trial. As you may know,
we've helped thousands of customers deploy serious production
applications in the cloud and would love to share some best practices
that we've learned along the way, including:

        * System Architecture
        * High Availability and Disaster Recovery
        * Software Versions
        * Database Recommendations
        * Third Party Services

Can we set up a quick call to discuss?

Your PANDA,

Will

If you believe this email was sent in error, click the following link
to manage your subscriptions [1].