title: Best Application Design for Software As Service
body: <p>Using ASP.NET MVC3 C# AND MS SQL 2008</p>
  
  <p>I'm developing a Software As Service site.  It's a Car Inventory app for Car Dealers.  I have a few ideas of the architecture of the site but wanted a second opinion.</p>
  
  <p>Each dealer will be restricted to a layout, but can upload a logo and select some color theme's.</p>
  
  <p>At first I thought about creating separate sites for each dealer, but upgrading would be a nightmare.</p>
  
  <p>So my thought is, one main site which dynamically changes based on the hostname.
  ie. So if miamicars.carinventory.com is entered, they would see their color scheme and logo.</p>
  
  <p>I would have one master database for the users and company settings, but a separate database for each site with the bulk of the data (car inventory, etc).  This way I can backup and handle each site's data individually, but the main code of the application would be in one place.</p>
  
  <p>Also, each company would have a directory to store their individual images.</p>
  
  <p>Any feedback would be welcomed.</p>
  
  <p>Thanks</p>