SugarCRM files and cache shared by multiple instances

Question

For our client we are building a solution that will consist of 2 SugarCRM nodes. We intend to share the full Sugar application folder from one instance to the other via NFS, so that they use a consistent file base. This will involve sharing the CACHE folder as well. Can this be a problem ?

Only one of the two instances will be available for doing Studio changes or Quick Repair & Rebuild. The other instance will only be interacted with via the REST API. Both instances will share the same database.

Looking forward to any tips&tricks, help/comments much appreciated.

Best regards,

Piotr

Piotr G · Accepted Answer

Sharing the whole Sugar application directory between web servers is the usual approach. I've also seen separation of front-end web servers from those that drive APIs. Our biggest on-site deployments do this. Keep in mind that you'll only want CRON running on one web server at a time. Sometimes this is deployed on it's own dedicated web server too. You want to have the cache directory shared across those servers. You can't allow it to be out of sync between web servers.