Advantages of Microsoft's Entity Framework in complex scenarios
I fail to see the advantages of Microsoft's Entity Framework in complex scenarios.
The examples that I saw were one database and pretty much a one-to-one mapping between entities and tables. Even then you still need to create business classes and then map your entity objects to your business objects (and then to DTOs in n-tier).
It appears that the only advantage here is the automatic creation of CRUD operations. This automation however falls short when you have complex scenarios such as data that is distributed across multiple databases or even when you have multiple joined tables within a one database.
It seems that in those scenarios you only save the ADO calls to (typically) stored procedures and perhaps the mappings of the SQL parameters. What am I missing?
Menashay Givoni, Feb 25, 2013