Entity Framework continues to grow in functionality. Using Code First, you can create a relational database from your Domain Objects and mappings, without knowing anything about a relational database engine.
Due to this very powerful capability, many developers are under the impression that they have made the role of a database developer obsolete. I experience it at work; I see it in blogs; I even get it in email.
While I find that tools such as EF are essential for reducing development time for applications, I find it has a narrow scope for behavior and performance. It is great for simple CRUD (Create, Retrieve, Update and Delete) operations. It can also handle other more complicated capabilities.
But, there are many other things that a DBA may do. The assertion that you can operate without a DBA, simply because you have Entity Framework, causes me have concern for those who have more than a simple application.
What do you think? Is a DBA obsolete in certain scenarios? Leave a comment to get into the conversation.
Cheers,
Ben