A Pure Object-oriented Domain Model by a DB Guy, Part 1
This is the first in a new series of articles by Jimmy Nilsson on a new architecture for enterprise applications in .NET. The new architecture is more purely object-oriented, while still focusing on roundtrips and the data access code to get good performance.
by Jimmy Nilsson
September 21, 2002
ore than a year has now passed
since I wrote
my book (.NET Enterprise Design with Visual Basic .NET and
SQL Server 2000[1].
The book discusses solutions to common design problems for
large-scale
applications, so several pages are spent discussing an
architecture that can be
used as a starting point for a new application. A year is
a long time in the
software industry, and it’s very long if you
consider that the .NET
Framework was in beta when my book was published.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ore than a year has now passed
since I wrote
my book (.NET Enterprise Design with Visual Basic .NET and
SQL Server 2000[1].
The book discusses solutions to common design problems for
large-scale
applications, so several pages are spent discussing an
architecture that can be
used as a starting point for a new application. A year is
a long time in the
software industry, and it’s very long if you
consider that the .NET
Framework was in beta when my book was published.
