Sevket Seyalioglu

After getting frustrated with the fact that Entity Framework and NHibernate does not resolve my needs, I am writing my own ORM tool to finalize one very important part of enterprise architecture.

Here are the features that are included (hope to finish by tomorrow)

1. Mutliple entity classes (one per each)
2. Single Data Provider Class
1. One Interface IDataProvider
2. One Class which inherits I[Model]DataProvider (SQL[Model]DataProvider)
1. [Model] to be renamed by the model name provided
3. One mocked class using moq framework (http://code.google.com/p/moq/)
3. SQL[Model]DataProvider will also implement retry logic in case of certain cases such as
1. Deadlock
2. Connection Timeout etc.
3. In a nutshell the following error codes : -1,-2,2,53,1222,1205
4. Will obviously generate related stored procedures and utilize them
5. Entities will be able to track simultaneous changes and will be able to throw exception if data changed before update!
6. Entities will implement [DataContract] & [DataMember] so that usage in WCF will be a lot easy
7. As you may see from here generated codes will implement Abstract Factory (Provider) design pattern and possibility of Singleton is also there.

I think it is time to test developers if they are up to date with proper design patterns.

And a question to all;

Do developers need to know design patterns or architects & leads would be enough to know?
(Here I am presenting this question to companies who has large number of teams, not for companies with less than 15 developers)