Rails - Jun 2006 - Nuby Q: Splitting of large projects for speed gains

Hi all,

Quick question - I have a project with a public front end, and an 
administrative back end. No need for them to be together. Would there be 
any speed gains on the hosting/serving side of things to keep them as 
separate projects?

Thanks in advance!

Cameron

-- 
Posted via http://www.ruby-forum.com/.

Cameron Booth wrote:
> Hi all,
> 
> Quick question - I have a project with a public front end, and an 
> administrative back end. No need for them to be together. Would there be 
> any speed gains on the hosting/serving side of things to keep them as 
> separate projects?
A few thoughts:

- Volume of admin use is usually very small compared with
   volume of public use. If this is true for you, the admin
   use won''t impact performance as seen by the public.

However,

- People often separate the admin app from the public app
   for security reasons. There may be an additional firewall
   between the public app and the internal network on which
   the DB and admin app live, and the admin app will connect
   as a different DB user, with write access where the
   public app only has read access.

- If the applications are separate, and the public app
   becomes overloaded, this won''t stop admin happening (so
   long as it''s not the database that is the bottleneck).

regards

   Justin