So then why have a business tier at all? If you are going to place all logic in a single stored procedure, or a single method call (that does not call other methods) you will have no modularity whatsoever.
-----Original Message----- From: Craig Andera [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 3:57 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Help Architecting A Middle Tier > I don't think spanning a transaction across multiple method > calls on the business tier is a problem as long as all those > alls are wrapped in a single call to the business tier that > starts and commits the transaction. Given that your database and your business tier machines are almost never one and the same, in fact having multiple method calls on the business tier can result in locks being held for dozens if not hundreds if not thousands of times longer than if all the transactional logic is contained in a single method/stored procedure. Long locks=bad scalability. And the real killer is that there's no way to cure it by adding more hardware. Database locking is the bottleneck to scaling in most systems, and it is best avoided by proper design. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
