Ideal n-tier hardware config for *devs*

Ever notice that the n-tier samples for developers are not truly intended for tiered distribution? Of course, that's because us devs don't have multi-machine environments to mirror what's actually used by our businesses (or customers). So, while the sample apps don't mirror real world, they do make handy demos. Can you imagine telling your boss / customer / spouse <g> that you need to have a dedicated development and test setup with, say, 4 machines and associated networking equipment? Would you really want to set up, configure, and manage this infrastructure?

What if you had - for example - 3 separate VMWare or Connectix images to simulate those 3 machines? What if you were able to simulate in software - using ISAS - the network firewalls separating those machine? Would that be cool?

So, what would you like to see on those images? Obviously an IIS Server and a SQL Server. And VS.NET installed in a separate image (or on a separate machine) because, after all, who's going to install VS.NET on a production server?

What would this "ideal" configuration really look like?  Let your mind run free: Don't worry right now about details like licensing. <g> Let me know in email (keithp@guideddesign.com) or by posting a comment to this entry

2 Comments

  • I use VMWare for testing. I keep a partition on my drive for just that purpose, nothing goes on it except VMWare 'machines'. It is a pain when you have to start with a fresh install, but that only happens occassionally and whenever I hose a VMachine so bad I have to delete it and start over. But installing on a VMachine is better than wiping out a real machine.


    My typical setup starts with Win2k Server or Win2k3 server, then .NET Framework 1.0 (I plan on skipping 1.1 if at all possible), then SQL Server 2000, then all the service packs. Sometimes I need to install Access and Crystal Reports (ack). I don't install VS.net on the servers, I work from a different machine.

  • Why skip .NET 1.1 ?

Comments have been disabled for this content.