This project is read-only.

Why Domain-Driver?

Why with the various .NET development frameworks available do we need one more domain modeling framework?

This is a very reasonable question you might ask yourself. Especially since the numerous frameworks available make it easier and easier to connect ASP .NET user controls to SQL Server records.

However, these database-to-GUI libraries make application development seem simple, but cause domain logic and GUI code to become inextricably tangled with infrastructure code and persistence technologies.

Enter Domain-Driver, which provides a discrete boundary which separates domain logic from persistence code, giving you the freedom to switch storage technology at any times with out affecting the behavior of your business logic or user-interface.

How Domain Driver Works
What Domain Driver Requires

Last edited Apr 11, 2011 at 6:40 AM by ryanse, version 10


No comments yet.