Wednesday, 30 December 2009

Options for Building Your Data Access Layer Using .NET

Thinking of building the data access layer of your next application?
What are your options?
What is most important to you; performance, scalability, security, flexibility, rapid development, etc?

Plain ADO.NET

Pros:
  • Use this option if performance is your main contain. No other solution would have higher performance than this as all tools will use plain ADO.NET internally.
Cons:
  • It's not rapid for development

ADO.NET Entity Framework

Pros:

Cons:

More:

Microsoft Enterprise Library Data Access Block

Pros:

Cons:

More:
Other references:

No comments: