----- Original Message ----- From: "Peter Foreman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 15, 2002 11:53 PM Subject: Re: [ADVANCED-DOTNET] Help Architecting A Middle Tier
[del] > Relational systems are at the heart of developing highly scalable systems. It does mean that code > and data to some extent are separated, and encapsulation is lost to a degree, but that is what is > required if you want to squeeze out every last drop of performance. Quite right. In fact, based on my experience I would replace "squeeze out every last drop" with "an order of magnitude increase in" > This is not to say OO analysis can not take place - I still use OOA to design this kind of system. > It just means that there is more of an indirect mapping between analysis and the implementation > model. Which reminds me of a question I've really been anxious to ask for quite some time: In many (maybe most?) enterprise systems, tiers are built by different developers. E.g. HTML/ASP/ASP.NET is written by one guy, business logic (VB com(+), VC/ATL com(+), C#. VB.NET) by another, and database structure and stored procs - by yet another. Yet, for scalable systems, when implementing a feature you have a mix and match between all three tiers, and ultimately all developers need to understand issues in all of them (data/biz/prez). So how do we (philosophically) solve this contradition? You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
