It is not true to say that:

"Unfortunately in this day & age we still don't have relational databases that allow us to divide our various objects into different name spaces"

Sql Server has Schemas that can be used to place objects in! Tables and SP and Functions. Look at AdventureWorks for examples.

Oracle (swearing tis tis) has tablespaces and packages,but the effect is the same.

So it is preferred that prefixes aren't used and schemas are.

But this article doesn't take other aspects of architecture into account.

For instance:

- data modeling with Entity Framework or nHibernate

- error and exception handling logging and reporting

- message management (error and non-error)

And these are relevant for a small to medium size application

Then what if the application is successful and needs to scale up and be extended.

can it:

use services as a layer of Interfacing

be seperated into different teirs that work in a application farm with a load balancer

call other services without too much plumping

use other tools or techiniques such sockets communication, multiple level threading, multiple UI eg ASP.net, Silverlight

All these need to be considered when considering architecture for a even a small application, else you are planning NOT to be successful or locking the applicaiton out of being extendable or scalable

regards

GregJF

PS

Ford now make all kinds of cars. If Henry was still alive, we would be all driving black cars that look alike.

Or Ford would be bankrupted long ago

Honda succeeds because it is innovative and changes its achitecture often, Honing, honing,honing!:-)